Remove Tag Instance From Person

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

The description reinforces annotations (destructiveHint: true) by stating 'This cannot be undone' and 'Permanently removes...'. It adds useful context beyond annotations, such as the API endpoint and required parameters, without any contradiction.

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 contains redundancy by repeating 'This cannot be undone' and 'Permanently removes...' twice. It also includes API endpoint info which, while useful, adds length. Could be more concise without losing essential information.

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 delete operation with no output schema, the description adequately covers the action, permanence, and required parameters. It lacks details on success/failure responses but is generally 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% with good parameter descriptions. The description merely lists the required parameters without adding additional semantic meaning, so it meets the baseline but does not enhance 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 'Remove Tag Instance from Person' and explains it permanently deletes Resource Planning records. The verb 'remove' is specific and the resource is well-defined, distinguishing it from sibling tools like 'add_tag_instance_to_person' and 'remove_tag_instance_from_project'.

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 warns that the action 'cannot be undone' and lists required parameters, providing clear guidance for use. However, it does not explicitly discuss when to avoid using this tool or compare it to alternatives, leaving some room for ambiguity.

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