add_labels

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

No annotations provided; description states the tool adds labels and references prerequisite, but does not disclose whether labels are additive vs. replacing, required permissions, or error scenarios. Some behavioral context is implied but not explicit.

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 sentences with no waste: first sentence states purpose, second provides usage guidance. Front-loaded and efficient.

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?

Low complexity (2 params), no output schema needed for mutation. Coverst purpose, prerequisite, and alternative tool. Could mention return value or side effects but adequate.

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 both parameters with descriptions (100% coverage). Description adds value by specifying that labelTypeIds should be obtained from get_label_types, providing meaningful context beyond the schema.

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?

Clear verb+resource ('Add category labels to a thread') and mentions prerequisite tool (get_label_types) and alternative tool (update_thread_labels), distinguishing it from siblings.

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?

Explicitly instructs to use get_label_types first to discover available label type IDs and recommends preferring update_thread_labels for combined add/remove operations.

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