get_slow_traces

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

With no annotations, the description carries the full burden. It usefully discloses defaults (min_duration_ms=1000, limit=10), the return format ('JSON string with slowest traces sorted by duration'), and the Jaeger requirement. However, it does not state read-only behavior, auth needs, rate limits, or error behavior.

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 front-loaded with the core purpose, then uses compact Args and Returns sections. Every line adds needed information given the zero schema description coverage, with no filler.

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?

For a simple trace-query tool with no annotations, the description covers all parameters, defaults, required context, and return shape. It is nearly complete, though it still lacks routing guidance against sibling tools and any safety or read-only confirmation.

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 0%, so the description must carry all parameter meaning. It documents all four parameters with clear semantics: service_name is required for Jaeger, operation_name filters, min_duration_ms is a threshold defaulting to 1000ms, and limit caps returned traces at 10.

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 and resource: 'Find slowest traces for a service.' The 'slowest' qualifier distinguishes it from generic trace search, but it does not explicitly name or contrast with siblings like search_traces or get_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 description gives no guidance on when to use this tool versus alternatives such as search_traces, get_trace, or find_errors. It only implies usage through the verb 'Find slowest traces' and adds a Jaeger requirement note, which is a constraint rather than usage guidance.

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