Tag post

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

Annotations already declare idempotentHint=true and destructiveHint=false; the description adds concrete meaning by saying a post can have several tags and tagging twice keeps one tag. It does not cover permissions or error behavior, but with annotations present this is useful added context.

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 and front-loads the add/remove action, but the first two sentences partly repeat the same idea. The behavioral sentences earn their place, so it is efficient overall but not maximally tight.

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 simple three-parameter mutation with rich annotations and no output schema, the description covers scope (draft/published), remove behavior, multiple tags, and idempotency. Nothing critical for correct invocation appears missing.

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%, so post_id, tag_id, and remove are already documented. The description only echoes that remove takes the tag off and that tag_id refers to one of your post tags, adding little beyond what the schema provides.

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 states a specific verb and resource ('Add a tag to a post, or take it off') and clarifies that it assigns existing post tags to draft or published posts. This implicitly separates it from create_post_tag (which creates a tag) and tag_subscribers (which targets subscribers), so an agent can distinguish it from siblings.

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?

It explains the remove parameter and that it works on draft or published posts, but it does not explicitly say when to choose tag_post over create_post_tag or list_post_tags, nor does it name alternatives. Usage is implied rather than fully guided.

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