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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description's 'take it off' is consistent with that. However, it adds no context beyond annotations — it does not warn that the remove path is destructive, nor mention idempotency behavior (re-adding a tag) or auth needs.

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 short sentence with the toggle behavior front-loaded and no filler. Nothing wasted.

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 3-param mutation tool with no output schema, the description covers the core action but says nothing about the result state (what the post looks like after tagging), failure modes, or idempotency. Annotations carry the safety profile, so this is adequate but thin.

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 100%, so all three parameters (post_id, tag_id, remove) are documented in the schema itself, including default and source tools. The description contributes nothing beyond that, so baseline 3 applies.

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?

Clear verb+resource: add or remove a tag association on a post. It distinguishes itself implicitly from create_post_tag (which makes the tag itself) via the schema reference, but the description never names a sibling to disambiguate tag_post from tag_subscribers or create_post_tag.

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?

Usage is implied by the toggle phrasing, but there is no explicit guidance on when to use this versus create_post_tag or list_post_tags, and no exclusions. The 'remove' flag is described in the schema, not the description.

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