zia_get_sandbox_report

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

Annotations already provide readOnlyHint=true. The description adds '(read-only)' which is redundant. No additional behavioral traits (e.g., response format, rate limits, error handling) are disclosed beyond what annotations and schema already convey.

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 concise sentence. However, it lacks structured breakdown of parameters or usage context. While efficient, it could be slightly more informative without added length.

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 security analysis tool with three parameters and no output schema, the description is too brief. It does not explain what the report contains, the difference between 'summary' and 'full' report details, or typical use cases. More context is needed for effective agent use.

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% with descriptions for all three parameters. The description does not add new meaning beyond the schema; it only mentions 'specific MD5 hash', which is already in the schema. Baseline 3 applies as schema already does the heavy lifting.

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 verb 'Retrieve', the resource 'sandbox analysis report', and the key parameter 'MD5 hash'. It distinguishes from sibling tools like 'zia_get_sandbox_behavioral_analysis' and 'zia_get_sandbox_rule' by specifying the exact input and read-only nature.

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 provides no guidance on when to use this tool versus alternatives such as 'zia_get_sandbox_behavioral_analysis' or 'zia_get_sandbox_file_hash_count'. No context on prerequisites or complementary tools.

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