add_label

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

The description merely restates the tool's function ('Add a label to a card') and adds no details about side effects, prerequisites, idempotency, or error conditions. With no annotations provided, this is a significant gap for a mutation 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?

Two short sentences that effectively convey the core action and a use case without redundancy. Every word earns its place.

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?

The description is adequate for a simple 2-required-param mutation, but it lacks behavioral context and fails to address the existence of sibling 'add_label_to_card', making it incomplete for an agent choosing between similar tools.

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% of parameters with descriptions, so the baseline is 3. The description adds no additional parameter semantics beyond what the schema already 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 states 'Add a label to a card' with a clear verb and resource, and adds a use case 'categorize a card'. However, it does not differentiate from sibling tool add_label_to_card, which appears to have the same function, so it's not fully distinct.

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?

Provides a usage context ('Use this tool to categorize a card') but no exclusions or guidance on when not to use it, nor does it distinguish from the similarly named sibling 'add_label_to_card'. This leaves ambiguity for an agent.

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