Rotate an app signing secret

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

Adds critical behavioral detail: 'The old secret stops working immediately', which goes beyond the destructiveHint annotation. Also mentions scope requirement, though schema annotations already indicate non-read-only and destructive nature.

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, 15 words, with front-loaded purpose. No redundant information.

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 rotation tool with 2 required parameters, the description provides the essential action, effect, and requirement. No output schema needed. Slightly lacking in explaining the return value but acceptable.

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 already fully describes both parameters (id, mode) with details like UUID format and enum values. The description does not add extra semantic meaning beyond referencing 'mode'.

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 uses a specific verb 'Rotates' and identifies the resource 'signing secret' for a single mode, clearly distinguishing this action from sibling tools like 'update_app' or 'switch_app_mode'.

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?

Clearly states the required 'ussd' scope and implies use when rotating a secret for a specific mode. However, no explicit guidance on when not to use or alternatives is provided.

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