Update Domain

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

Description adds value beyond annotations by warning 'Changing the catch-all silently retargets all unmatched-recipient mail; treat as destructive.' This clarifies the destructive behavior beyond the destructiveHint=true annotation. Idempotency is not mentioned but is covered by annotation.

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 short sentences with no waste. First sentence states purpose, second adds critical behavioral context. Front-loaded and efficient.

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 presence of annotations and output schema, the description covers the essential behavior. It explains the core update capability and the destructive side effect. No gaps for an agent to invoke correctly.

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 description coverage is 100%, so baseline is 3. The description mentions the catch-all mailbox but does not add meaning beyond the schema's own parameter descriptions (e.g., 'Mailbox ID to receive catch-all mail, or null to clear.').

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 'Update mutable domain settings, currently the catch-all mailbox.' This specifies the verb (update) and resource (domain settings), and differentiates from sibling tools like create/delete/get domain by focusing on updates.

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 explicit when-to-use or alternatives provided. The name implies update, but the description does not contrast with shipmail_create_domain or shipmail_delete_domain. However, the sibling list makes the domain-specific context clear, earning a baseline score.

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