add_project_label

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

Annotations provide openWorldHint, and description states the basic action. No contradictions, but lacks details on side effects or required permissions. Adequate given simplicity.

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?

Single sentence, no extraneous text, front-loaded with action and target.

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?

Despite having output schema, description omits important context (e.g., prerequisites like label existence, what 'attach' means). Leaves gaps for a new user.

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% and description does not explain the purpose of project_id or label_id, nor how to obtain them. Baseline of 3 cannot be maintained when coverage is low.

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 'Attach an existing project label to a project' specifies a clear verb ('Attach') and distinct resource ('project label to a project'), distinguishing it from siblings like add_issue_label and create_project_label.

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 on when to use this tool instead of alternatives (e.g., add_issue_label vs add_project_label). Missing context like label must already exist.

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