wealthbox.contacts.delete

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. 'Delete contact' only states the action and does not mention irreversibility, permission requirements, or potential cascading effects on related data. This is a significant gap for a destructive operation.

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 extremely concise at two words, with no redundant content. It is front-loaded and easy to parse. While slightly under-specified, it remains efficient for a simple tool, though it could include minimal context without sacrificing conciseness.

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 this is a destructive operation with no annotations and no output schema, the description is insufficient. It does not convey important context such as irreversibility, permissions, or the impact of deleting a contact, leaving the agent with incomplete information to correctly invoke the 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?

The schema defines a single 'id' parameter of type number with no description, and schema description coverage is 0%. The description does not explain what 'id' refers to or any format constraints. The parameter's purpose is implied by the tool name, but the description adds no explicit semantic value.

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 'Delete contact' clearly states the action (delete) and the resource (contact). It is specific and not a tautology, but it does not distinguish itself from other delete tools such as wealthbox.events.delete or wealthbox.tasks.delete, though the resource name provides reasonable differentiation.

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 guidance is provided on when to use this tool versus alternatives like update or other delete tools. There are no prerequisites, exclusions, or context about selecting this over a similar sibling tool.

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