remove_tag_taxonomies

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

No annotations are provided, so the description carries full burden. It states the core action but fails to disclose side effects (e.g., whether the tag itself is deleted, if it affects child tags, required permissions, or idempotency). This is a significant gap for a mutation tool.

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?

A single sentence of 10 words with no filler. It is front-loaded and immediately conveys the purpose.

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 the tool's simplicity (one parameter, no output schema), the description is adequate but minimal. It does not mention return values, error cases, or the tag's status after detachment, leaving some ambiguity. More detail on effects would improve completeness.

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 describes the parameter as 'ID of the resource,' which is generic. The description clarifies that the ID refers to a tag, adding meaning beyond the schema. Schema coverage is 100%, but the description provides necessary context for the resource type.

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 uses a specific verb 'Detach' with a clear resource 'a tag' and target 'all taxonomies it belongs to.' This precisely distinguishes it from sibling tools like 'delete_taxonomy_tag' or 'remove_tag_face_membership'.

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 implies when to use this tool (when wanting to remove a tag from all taxonomies), but it does not explicitly state when not to use it or mention alternatives like 'delete_taxonomy_tag' or 'add_tag_to_taxonomy'.

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