Create Content Tag

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

Annotations provide minimal info (non-readonly, non-destructive, non-idempotent, open world). Description adds no behavioral context beyond what annotations imply, such as what happens if tag already exists or side effects.

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 a single sentence, which is concise but lacks additional context that could improve usability. It is not overly verbose but also not optimally informative.

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 tool with one parameter and no output schema, the description covers the basic action. However, missing behavioral details (idempotency, duplicate handling) and usage guidance leave 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?

The only parameter 'name' is already described in the schema as 'Content tag name' (100% coverage). Description adds no extra meaning 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 'Create a new content tag for Guide articles' clearly states verb (create), resource (content tag), and context (for Guide articles). It distinguishes from siblings like list_content_tags and manage_tags.

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?

No guidance on when to use this tool versus alternatives (e.g., manage_tags) or any prerequisites. No mention of duplicate handling or required permissions.

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