set_recovery_address

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

Describes the effect (auto-drain on deletion) and that address can be set or cleared, but does not disclose side effects (e.g., whether setting overrides previous value, permissions required, or if operation is idempotent). No annotations to supplement.

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?

Single sentence front-loads the action ('Set or clear') and purpose, with no wasted words. Efficient and to the point.

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?

Description adequately covers the tool's purpose and input parameters for a simple set/clear operation. Without output schema, it could mention return value or confirmation, but completeness is high for this straightforward tool.

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 describes all three parameters (project_id, signer_id, recovery_address) with clear descriptions. Tool description adds overarching context but no additional detail beyond schema; baseline appropriate given 100% 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?

Clear verb 'Set or clear' with specific resource 'recovery address for a KMS signer', and explicit purpose for auto-drain on day-90 deletion. Distinguishes from sibling tools like 'drain_signer' by focusing on address assignment rather than actual drain.

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?

Implied when to use (when needing to manage recovery address for auto-drain), but lacks explicit guidance on when not to use, prerequisites (e.g., signer must exist), or comparison with alternative tools like 'drain_signer'.

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