zdx_get_analysis

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

Annotations already provide readOnlyHint=true and openWorldHint=false. Description adds 'Returns whether the analysis is still running or its results if complete', which is useful but not extensive. No contradictions, but lacks detail on potential side effects or rate limits.

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 sentences: first states purpose, second adds behavioral detail and sibling reference. Front-loaded, no wasted words, highly 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?

Has output schema (indicated true) so return values are covered. Low complexity with one param and simple read operation. Description explains the two states (running vs complete), but could mention the need for analysis_id from zdx_start_analysis.

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?

Only one parameter (analysis_id) with 0% schema coverage in description. The description does not elaborate on its meaning or origin (e.g., 'ID from zdx_start_analysis'). With low coverage, description should compensate but fails to add value beyond 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 'Get the status/result of a ZDX score analysis (full record)', specifying the verb (Get), resource (ZDX score analysis status/result), and scope (full record). It distinguishes from siblings by mentioning zdx_start_analysis as the complementary tool to start an analysis.

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 says 'Read-only' and describes when to use (retrieve status/results) and how to start one with zdx_start_analysis. Clear context but lacks explicit 'when not to use' or prerequisites like requiring analysis_id from a started analysis.

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