obs_get_trace

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Fetch', which implies a read operation, but it does not describe what happens if the trace does not exist, whether a connection/session is required, or any side effects. The agent is left without important behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one short sentence with no filler or redundancy. It front-loads the core action and resource, making it immediately scannable for an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although the output schema is present, the description omits enough contextual detail for an agent to invoke the tool correctly in a broader workflow. It does not explain session_name, connection prerequisites, error behavior, or how this tool fits among its observability siblings. For a tool with no annotations, this leaves the agent undersupported.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for the limited input schema. It clarifies that trace_id is the identifier used for lookup, but it does not explain the format or semantics of trace_id, nor does it explain the optional session_name parameter or its default behavior. This is insufficient given the lack of schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Fetch'), a specific resource ('one Tempo trace'), and the key selector ('by id'). This clearly differentiates it from the sibling tool obs_search_traces, which is about searching rather than fetching a single known trace.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'by id' implies the tool should be used when a specific trace ID is already known, which provides implicit usage context. However, it does not explicitly state when not to use it, nor does it mention alternatives like obs_search_traces for finding traces without an ID.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.