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

Despite having no annotations, the description discloses a key behavioral trait: idempotency. It explicitly states that if the tag already exists, it returns the existing one without duplicating. This adds context beyond the schema, though it does not cover permissions or response format.

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 that front-loads the core purpose and appends the idempotency behavior in parentheses. Every word earns its place, with no filler.

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?

While the tool is simple, the description lacks usage guidance and parameter semantics. It also does not mention return values or potential errors, and with no annotations or output schema, it carries more burden. The idempotency note is helpful but incomplete.

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 schema description coverage is 0%, and the description does not explain the 'name' or 'color' parameters. It only mentions creating a tag and idempotency, leaving parameter semantics entirely to the schema's bare 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?

The description states 'Crea una etiqueta' (creates a tag), using a specific verb and resource. It clearly distinguishes from sibling tools like create_flow or create_list by explicitly naming 'tag' as the resource.

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 is provided on when to use this tool versus alternatives. The description only mentions idempotency but does not discuss use cases, prerequisites, or exclusions. Sibling tools like tag_subscribers or create_subscriber exist, but no differentiation is given.

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