Get Ops Trace Run

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds minimal context beyond the annotations, such as that it fetches a specific run, but does not disclose return format, pagination, or other behavioral details. With annotations present, a score of 3 is appropriate.

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 a single sentence with no redundant words, front-loaded with the verb 'Fetch'. It is highly concise and efficient.

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 read-only tool with two well-described parameters and no output schema, the description is mostly complete. However, it could benefit from explaining what a 'run' is or how trace_id and run_id relate, especially given the large number of trace-related sibling tools. Slight gap but generally adequate.

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?

The schema provides 100% coverage of the two parameters with descriptions 'Run id' and 'Trace id'. The description does not add additional meaning about parameter relationships, formats, or constraints. Baseline 3 is appropriate since the schema already documents the parameters.

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 uses a specific verb ('Fetch') and identifies the resource ('a specific run within a trace'), making the action clear. It is somewhat distinguishable from sibling tools like lyzr_get_trace_summary or lyzr_get_trace_details, but it does not explicitly compare against these alternatives.

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?

No guidance is provided about when to use this tool versus other trace-related tools. There is no mention of use cases, prerequisites, or when to prefer an alternative like lyzr_ops_get_trace or lyzr_get_trace_details.

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