Contacts Delete Contact

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

The description adds no behavioral information beyond the annotations. destructiveHint=true already signals a destructive operation and idempotentHint=false signals non-idempotency, but the description does not add context about what exactly is destroyed, whether deletion is permanent, or what permissions are needed.

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 short but is mostly boilerplate: 'Delegated Apple domain tool... exposed through Apple-Tools-MCP' earns no real value and does not front-load the tool's actual purpose. This is under-specification rather than effective 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?

For a destructive one-parameter tool, the description is not complete enough. The annotations cover the destructive nature and the output schema may cover return values, but the description fails to state the core operation, usage context, or effect on the contact resource.

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 0%, so the description needed to compensate, but it says nothing about the contact_id parameter. The parameter name and title make it reasonably clear, but the description provides no extra meaning about the expected format or where the ID comes from.

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 does not state that the tool deletes a contact; it only restates the tool name as a 'Delegated Apple domain tool' exposed through a wrapper. The eventual action is inferable from the name and title, but the description itself provides no specific verb+resource statement.

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?

There is no guidance about when to use this tool instead of contacts_update_contact, contacts_list_contacts, or contacts_search_contacts. No prerequisites, such as obtaining a valid contact_id, are mentioned.

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