tag_create

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

With no annotations, the description must disclose all behavioral traits. It labels the tool 'Mutating' and mentions 'bridge plane', but fails to explain side effects (e.g., whether existing tags are overwritten), permission requirements, or the meaning of the 'confirm' parameter. The output schema is present but not described.

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 very concise (2 sentences) but at the expense of completeness. It is not verbose, but it omits critical details about parameters and usage. For a mutating tool with 4 parameters, it is too sparse.

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?

Given the complexity (mutation tool, multiple parameters, no annotation support), the description is incomplete. It does not explain the output, the collision policy behavior, or how to safely use the confirm flag. The presence of an output schema is unaddressed, leaving the agent with significant unknowns.

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 description coverage is 0%, so the description should add meaning. It hints that 'tags' are dicts, but provides no explanation for base_path, confirm, or collision_policy. The default values in the schema are not explained. The description adds minimal value beyond the schema structure.

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 verb 'Create or update' and resource 'tags'. It also specifies input format 'from config dicts', which distinguishes it from siblings like tag_write which likely handles single tags. However, it does not explicitly contrast with tag_import or tag_config_import.

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 explicit guidance on when to use this tool vs. alternatives like tag_write or tag_config_import. The description assumes context but provides no when-to or when-not-to advice. The agent is left to infer the difference from the 'config dicts' phrase.

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