get-trace

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

Describes return content ('timing, service, resource, and error information') but does not disclose potential behavioral traits like pagination, limits, or side effects. With no annotations, the description provides adequate but not comprehensive transparency.

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?

Two concise sentences: first states purpose, second provides usage context and return information. No redundant or unnecessary text.

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?

Given 3 parameters and no output schema, the description explains what is returned and when to use. It leverages schema descriptions for parameters. Could mention ordering or limits, but overall complete for typical use.

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 coverage is 100% and each parameter has a description in the schema. The description does not add further meaning to the parameters (e.g., explains traceId is required, from/to are optional with defaults). Baseline 3 is appropriate.

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?

Clearly states 'Get all spans for a specific trace ID.' and distinguishes from sibling search-spans by explaining it is used after search-spans to see the full request flow. Defines specific verb and resource.

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?

Explicitly tells when to use: 'Use after search-spans to see the full request flow across services.' Provides clear context, though it does not explicitly mention when not to use or list alternatives beyond search-spans.

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