Move a contact to another address book

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

The description goes well beyond annotations by revealing the non-transactional nature: 'the copy is verified before the original is removed.' It also explains the id change, which is a surprising side effect. This is valuable behavioral context beyond the destructiveHint 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?

Three concise sentences with no wasted words. The first sentence states the core action, the second explains a key side effect, and the third warns about the non-transactional behavior. Information is front-loaded and each sentence adds value.

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 that the output schema exists and annotations mark the operation as destructive, the description covers the essential behavioral quirks: non-atomcity and id change. It does not explicitly state prerequisites or alternatives, but the schema and annotations carry most of the remaining burden, making the description appropriately 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?

Schema coverage is 100%, so the schema already documents all three parameters. The description adds context about the id changing, which helps explain id semantics, but it does not clarify destination or confirm_token further. This meets the baseline for high schema coverage without adding much parameter-specific detail.

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: 'Copies a card into another address book and removes it from the first.' This distinguishes it from delete_contact, create_contact, and update_contact. The note about id changes reinforces the move semantics.

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 title and description make the use case obvious, but no explicit guidance is given about when to use this tool versus alternatives like delete_contact or create_contact. The description does not mention exclusions or alternative tools; it relies on the word 'move' to imply the scenario.

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