Get Trace Details

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety behavior is covered. The description adds minimal extra context ('raw details') but does not disclose return format, potential errors, or relationship to trace lifecycle.

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?

A single, focused sentence front-loads the action and resource with no filler or redundant information.

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 the simple single-parameter lookup, rich annotations, and full schema coverage, the description is mostly complete. It could mention how to obtain trace_id or what 'raw details' includes, but the low complexity lowers the burden.

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%; the trace_id parameter is already described as 'Trace id'. The description adds no meaning beyond 'by id', so it provides no extra value over the schema.

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 clearly states the action ('Fetch'), the resource ('raw details for a trace'), and the lookup method ('by id'). The phrase 'raw details' helps distinguish it from sibling tools like lyzr_get_trace_summary and lyzr_get_trace_gantt.

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 implies usage when you need raw trace details and already have a trace_id, but it does not explicitly mention when to prefer it over alternatives like get_trace_summary or get_trace_gantt. There is no exclusion or alternative guidance.

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