zia_get_activation_status

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

The description adds the qualifier "read-only" which aligns with the readOnlyHint annotation. However, it does not disclose any other behavioral traits such as authentication requirements, rate limits, or effects beyond what annotations already provide.

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 with no unnecessary words. It is front-loaded and efficiently communicates the tool's purpose.

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 read-only getter with an optional parameter and an output schema present, the description is adequate. It covers the core purpose, though it does not elaborate on the nature of the activation status or any prerequisites.

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 single parameter 'service' is fully described in the input schema (100% coverage). The tool description does not add any additional meaning or context beyond what the schema already provides, so the score is at baseline.

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 it retrieves the ZIA configuration activation status and specifies it is read-only. It uses a specific verb and resource, distinguishing it from other get_* tools in the sibling list.

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?

No guidance on when to use this tool versus alternatives (e.g., other get_* ZIA tools). The description simply states what it does without context or exclusion criteria.

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