Create Content Tag

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

Discloses that content tags are end-user visible and returns the created tag with id. Annotations already indicate readOnlyHint=false and destructiveHint=false, so description adds value about visibility and return behavior. Lacks details on rate limits or permissions but acceptable for a simple creation tool.

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 well-structured sentences: first states purpose and return, second gives workflow guidance, third distinguishes from alternatives. No redundancy. Front-loaded with key action.

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?

Despite no output schema, description explains the return value (created tag with id). Provides full workflow context (check duplicates, attach to articles) and alternative tool reference. Complete for a simple creation tool.

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 covers 100% with description for 'name'. Description adds concrete examples ('billing', 'getting-started') and context about end-user visibility, enhancing the schema's explanation.

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?

Description clearly states the tool creates a new content tag for Guide articles and explains what content tags are. It uses specific verb 'Create' and resource 'content tag', and distinguishes from article labels (list_labels) mentioned later.

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?

Explicit guidance to check list_content_tags first to avoid duplicates, then use the returned id with create_article or update_article. Also clarifies when to use article labels instead for internal tags. Provides clear when and when-not scenarios.

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