create_tag

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

Annotations already convey readOnlyHint=false and destructiveHint=false, so the safety profile is known. The description adds no new behavioral traits: no mention of return values, error handling, duplicate-name behavior, authentication requirements, or side effects beyond 'create a new tag'. It restates the obvious mutation without enriching the behavioral model.

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, concise sentence with the primary action front-loaded ('Create a new tag'). It lists the optional features without unnecessary detail, making it efficient to parse. It earns a 4 rather than 5 because it could more explicitly mention the required name field or the hierarchical 'parent' option in the same space.

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 tool with 6 parameters, no output schema, and only two generic annotations, the description is thin. It fails to mention that 'name' is required, what the tool returns (e.g., the created tag or ID), or any side effects like automatic matching configuration. The schema carries some parameter explanations, but the description does not fill the missing behavioral and output context.

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?

With 50% schema description coverage, the description adds some meaning: it labels 'match' as a 'matching pattern' and connects 'matching_algorithm' to automatic tagging, which aids understanding beyond the schema. However, it doesn't explain 'name', 'parent', or 'is_insensitive', which the schema partially covers. It adds value but not comprehensive compensation for the undocumented parameters.

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: 'Create a new tag'. It also names the key optional fields (color, matching pattern, matching algorithm) and the purpose ('automatic document tagging'), which clearly distinguishes it from read-only and update/delete tag siblings. This is unambiguous and resource-specific.

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 description gives no explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives like update_tag or edit_tags_bulk. The phrase 'for automatic document tagging' hints at the tag's intended role but does not help an agent decide between this and other tag-related tools.

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