zdx_get_deeptrace_events

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

Description adds '(read-only)' which aligns with annotations (readOnlyHint=true). No additional behavioral traits beyond that, such as 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?

Single sentence with 10 words, front-loaded with verb and resource. Efficient, though slightly under-specified for broader context.

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?

Output schema exists, so return values are covered. Schema coverage is high. However, description lacks usage context like required parameters (though schema specifies). Adequate for a simple tool.

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 has 100% description coverage with clear descriptions for all 3 parameters. Description does not add extra meaning beyond the schema, meeting baseline for high coverage.

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?

Description clearly states 'Get events from a ZDX deep trace session (read-only)', specifying the verb (get), resource (events from deep trace), and safety hint. This distinguishes it from sibling tools like zdx_get_deeptrace_cloudpath.

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 explicit when-to-use or alternatives provided. The name and description imply usage for retrieving events from a specific trace, but no guidance on prerequisites or context.

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