Remove Contact Property

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

With no annotations provided, the description carries the full burden. It discloses critical behavioral traits: the action is irreversible and removes the property from all contacts. It also emphasizes the need for user confirmation. However, it doesn't describe return values, error conditions, or potential restrictions beyond irreversibility.

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 sentences, with the purpose stated first, followed by focused safety instructions. Every sentence earns its place; there is no redundancy or unnecessary detail.

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?

For a simple one-parameter destructive tool with no annotations or output schema, the description covers key context: irreversible impact, all-contacts scope, and confirmation workflow. It could mention error cases (e.g., property not found) or whether some properties are protected, but overall it is quite complete given the tool's simplicity.

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% for the single parameter contactPropertyId, so the baseline is 3. The description adds a useful nuance by instructing to reference the property KEY during double-checking, implying a distinction between ID and key, but it doesn't elaborate on parameter format or validation beyond what the schema provides.

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 ('Remove'), the resource ('contact property'), and the method ('by ID'). It distinguishes from sibling tools like update-contact-property, get-contact-property, and create-contact-property by specifying removal.

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?

Provides explicit prerequisites: double-check with the user, reference the property KEY, warn about irreversibility and impact, and only proceed with explicit confirmation. This defines when not to use the tool, but it doesn't name alternatives or contrast with update/delete operations, so it's not a full 5.

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