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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety profile is known. The description adds a useful behavioral detail beyond annotations: the tag is automatically detached from documents and templates when deleted, clarifying the side effect. It does not discuss irreversibility or permission requirements, but the added context is meaningful.

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?

Front-loaded with the purpose, then a short usage bullet, then the side effect. Three sentences with no wasted words, and the most important information is stated first.

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 available output schema, annotations, and 100% schema description coverage, the description supplies purpose, trigger condition, and the key side effect of automatic detachment. It omits reversibility details and prerequisites, which are largely covered by destructiveHint=true, leaving only minor gaps.

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% and the single parameter tag_uuid is fully documented in the schema. The description does not add format, syntax, or lookup guidance for the UUID, so it meets the baseline of 3 when the schema carries parameter semantics.

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?

States a specific verb and resource: 'Delete an existing tag.' This distinguishes it from sibling tools like create-account-tag, update-account-tag, list-account-tags, and delete-account-document-type by both action and resource. The side-effect sentence further confirms the account-level tag scope by mentioning detachment from documents and templates.

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 an explicit usage trigger: 'Use this tool when: - The user explicitly asks to delete a tag.' It lacks when-not guidance and does not name an alternative tool such as update-account-tag, but the context for use is clear.

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