zia_get_sandbox_rule

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

Annotations already indicate this is a read-only operation (readOnlyHint: true). The description adds that the response includes 'member references', but does not elaborate on other behavioral aspects such as error handling or response structure. It does not contradict annotations.

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, well-structured sentence that conveys the essential information without any filler. It is front-loaded and 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?

Given the tool's simplicity (one parameter, no output schema), the description is minimally adequate. However, it could be improved by hinting at the response format or noting that the rule object contains detailed settings. It does not fully capture what the agent might need to know about the output.

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?

The only parameter, 'rule_id', has no description in the schema (0% coverage) and the tool description does not provide any additional context about its format, expected values, or source. The name alone is insufficient for an agent to know how to populate it correctly.

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 ('Get'), the resource ('ZIA Sandbox rule'), and the method ('by ID'). It also mentions 'with member references', which adds specificity. Among sibling tools like 'zia_list_sandbox_rules' and other get functions, this description sufficiently distinguishes the tool.

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 the tool is used to retrieve a single Sandbox rule by its ID, but it does not explicitly state when to use this over alternatives like 'zia_list_sandbox_rules'. No guidance on when not to use or prerequisites is provided.

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