some fixes

Author: lmolkova

tox.ini

@@ -789,8 +789,6 @@ deps =
 
   util-genai: {[testenv]test_deps}
   util-genai: -r {toxinidir}/util/opentelemetry-util-genai/test-requirements.txt
-  util-genai: -e {toxinidir}/util/opentelemetry-util-genai
-  lint-util-genai: -e {toxinidir}/util/opentelemetry-util-genai
 
   ; FIXME: add coverage testing
 allowlist_externals =

util/opentelemetry-util-genai/AGENTS.md

@@ -36,16 +36,16 @@ Factory methods on `TelemetryHandler` (`handler.py`):
 
 - `start_inference(provider, request_model, *, server_address, server_port)` → `InferenceInvocation`
 - `start_embedding(provider, request_model, *, server_address, server_port)` → `EmbeddingInvocation`
+- `start_tool(name, *, arguments, tool_call_id, tool_type, tool_description)` → `ToolInvocation`
 - `start_workflow(name)` → `WorkflowInvocation`
-- For tool calls, construct `ToolInvocation` directly and call `invocation.stop()` / `invocation.fail(exc)`
 
-Context manager equivalents (`handler.inference()`, `handler.embedding()`, `handler.workflow()`) are
-available when the span lifetime maps cleanly to a `with` block.
+Context manager equivalents (`handler.inference()`, `handler.embedding()`, `handler.tool()`,
+`handler.workflow()`) are available when the span lifetime maps cleanly to a `with` block.
 
 ### Anti-patterns
 
-**Never construct invocation types directly** (`WorkflowInvocation(...)`, etc.) in
-instrumentation or production code — direct construction skips span creation and context
+**Never construct invocation types directly** (`InferenceInvocation(...)`, `ToolInvocation(...)`,
+etc.) in instrumentation or production code — direct construction skips span creation and context
 propagation, so all telemetry calls become no-ops. Always use `handler.start_*()`.
 
 ## 3. Exception Handling
@@ -56,26 +56,25 @@ propagation, so all telemetry calls become no-ops. Always use `handler.start_*()
   the original exception unmodified.
 - Do not wrap, replace, or suppress exceptions — telemetry must be transparent to callers.
 
-## 3. Documentation
+## 4. Documentation
 
 - Docstrings for invocation types and span/event helpers must include a link to the
   corresponding operation in the semconv spec.
 - When adding or changing attributes, update the docstring to describe what is set and under
   what conditions (e.g., "set only when `server_address` is provided").
 
-## 4. Tests
+## 5. Tests
 
 - Every new operation type or attribute change must have tests verifying the exact attribute
   names and values produced, checked against the semconv spec.
 - Cover all paths: success (`invocation.stop()`), failure (`invocation.fail(exc)`), and any
   conditional attribute logic (e.g., attributes set only when optional fields are populated).
 - Tests live in `tests/` — follow existing patterns there.
-- Don't call internal API in testswhen the public API is available.
+- Don't call internal API in tests when the public API is available.
 
-## 5. Python API Conventions
+## 6. Python API Conventions
 
 - Mark internal class methods, instance fields, and module-level helpers with a `_` prefix;
   anything without it is considered public API.
-- Use `field(init=False)` for fields set internally after construction.
 - Before removing or renaming a public symbol, deprecate it first with
-  `warnings.warn(..., DeprecationWarning, stacklevel=2)` pointing to the replacement;
+  `@deprecated("... Use X instead.")` pointing to the replacement;