zia_get_rule_label

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

The description explicitly says 'read-only', which is consistent with the annotation readOnlyHint=true. However, it does not add additional behavioral context beyond what the annotation already provides, such as potential errors, permissions, or side effects.

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 sentence that front-loads the action and resource, with no extraneous words. It is concise while being informative.

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 required parameter), the presence of an output schema, and annotations indicating read-only, the description covers essential context. It could benefit from mentioning error handling or required permissions, but is complete enough for its intended 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?

The input schema has 100% description coverage for both parameters (label_id and service). The description adds no additional parameter semantics beyond what is already in the schema, meeting the baseline for high schema 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?

The description clearly states the action (get), the resource (ZIA rule label), and the method (by ID). It distinguishes from sibling 'zia_list_rule_labels' by indicating retrieval of a specific label by its identifier, and notes the operation is read-only.

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 label ID, but it does not explicitly state when to use this tool versus alternatives like 'zia_list_rule_labels' for listing all labels, nor does it mention prerequisites or when not to use.

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