Rotate Voice Integration Secret

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

Annotations already indicate destructive and non-read-only behavior. The description adds valuable context by stating 'The response returns only a secret summary, never raw secret values,' which goes beyond the annotations and informs the agent about the response behavior.

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 concise: one main sentence plus an inline parameter list. Every word earns its place, and the main action is front-loaded.

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 only two parameters, a nested object, and an output schema, the description covers the essential intent and the notable response behavior. It could mention prerequisites or side effects of rotation, but the existing annotations and the explicit note on response summaries make it fairly 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?

With 0% schema description coverage, the description provides basic meaning for both parameters: integration_id is 'the integration's id' and secrets are 'the new provider secret values.' This is helpful but lacks detail on format, required structure, or constraints for the nested secrets object.

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: 'Rotate a voice provider integration's secrets.' The verb 'rotate' is specific and distinct from sibling tools like connect, update, get, or delete, making the tool's purpose unambiguous.

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 usage for rotating secrets but gives no explicit guidance on when to use this tool versus alternatives like update_voice_integration. There is no mention of exclusions or when-not-to-use conditions, though the specific action is self-evident.

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