zia_get_sandbox_rule

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

The 'read-only' annotation is already provided, and the description repeats this. No additional behavioral traits (e.g., error handling, rate limits) are disclosed beyond what annotations provide. Contradiction is false.

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, front-loaded sentence with no unnecessary words. It efficiently conveys the core operation.

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 get-by-ID tool with full schema coverage and annotations, the description is sufficient. It does not explain return values, but the operation implies returning a rule object. However, it could be more complete by mentioning that it returns the full rule details.

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%, so the schema already describes the parameters. The description adds 'by ID' but does not provide extra meaning beyond the schema's parameter descriptions.

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 (Get), resource (ZIA Sandbox rule), and method (by ID). It distinguishes from siblings like 'zia_list_sandbox_rules' by specifying a single rule retrieval and includes 'read-only' for additional clarity.

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 use when you have a specific rule ID but does not explicitly state when to use this tool vs alternatives like 'zia_list_sandbox_rules'. No exclusions or preconditions are mentioned.

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