remove_contact

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

The description goes beyond annotations by detailing the removal process across chains, conditions for dropping unsigned metadata, error codes (CONTACTS_LABEL_NOT_FOUND), and Ledger pairing needs. It also references issue #428 for additional context. No contradictions with annotations.

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 detailed and well-organized, but slightly verbose. It front-loads the core action and then provides conditional explanations. Every sentence adds value, though some complexity could be streamlined.

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?

The description covers behavior and error conditions thoroughly but omits the return value or confirmation of success. Since no output schema exists, this gap reduces completeness for an agent expecting a response format.

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?

Both parameters have schema descriptions (100% coverage). The description adds extra meaning by explaining the effect of the chain parameter on removal scope and the concept of signed vs unsigned entries. This enhances understanding beyond the schema.

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 tool removes a labeled contact and distinguishes behavior with and without the chain parameter. It references siblings like add_contact and list_contacts implicitly, and the name is self-explanatory.

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 explicitly explains when to use the chain parameter (to remove from a specific chain) versus omitting it (remove from all chains). It also covers Ledger requirements for different scenarios. However, it does not explicitly mention when not to use this tool compared to siblings, though the context makes it clear.

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