zms_get_agent_group_totp_secrets

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

Annotations already declare readOnlyHint=true, so the description's 'Read-only API call' is consistent. It adds crucial behavioral context: the returned values are sensitive enrollment credentials that must be treated like secrets, and it requires ZSCALER_CUSTOMER_ID. No contradiction with 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?

Two sentences that are front-loaded, with the first stating the core purpose and the second adding essential caveats. Every sentence is valuable and there is no extraneous text.

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 has an output schema (not shown), the description correctly focuses on input and behavioral aspects. It mentions sensitivity, authentication requirement, and the key parameter. For a simple tool with one parameter, this is sufficiently complete.

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?

Input schema has 0% description coverage for the single parameter 'eyez_id'. The description only says 'Keyed by `eyez_id`', which adds minimal meaning (it is an identifier) but does not explain what the identifier represents, its format, or how to obtain it.

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?

Description clearly states the verb 'Get' and the specific resource 'TOTP secrets for a ZMS agent group (full record)'. It distinguishes from siblings by focusing on secrets for ZMS agent groups, which is unique among the listed sibling tools.

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?

Implicitly indicates usage via the parameter 'eyez_id' and mentions requiring 'ZSCALER_CUSTOMER_ID', but does not explicitly state when to use versus alternative tools 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.