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

Annotations already declare this is a non-read-only, non-destructive, closed-world write, so the safety profile is covered. The description earns credit beyond that by disclosing the 200-tag-per-workspace cap and case-insensitive uniqueness — both are failure conditions an agent should anticipate. It does not say what happens on a duplicate name (error vs. returning the existing tag).

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?

Three short sentences, front-loaded with the action, then constraints, then the alternative path. No filler and every sentence carries information the structured fields do not.

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 two-parameter creation tool with full schema coverage and no output schema, this is nearly sufficient: it explains what a tag is, naming rules, and the quota. The only real gap is duplicate-name behavior, which matters for a uniqueness-constrained create.

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 the baseline is 3, but the description adds real semantic constraints not present in the schema: name uniqueness within a workspace and case-insensitive comparison. That tells the agent a duplicate call is likely to fail or collide, which the schema alone does not convey.

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?

Opens with a specific verb+resource ("Create a post tag") and immediately grounds it with three concrete example tag names, so an agent knows exactly what object is being made. It is clearly distinguishable from sibling update_tag, delete_tag and list_tags by the verb and object.

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 final sentence routes the agent away from this tool when a tag can be created implicitly via create_post / update_post / tag_posts, which is genuine alternative guidance. It stops short of stating when to prefer this explicit call over the implicit path (e.g. pre-creating a palette of tags before tagging).

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