add_repository_labels

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

No annotations exist, so description carries full burden. It mentions creation (write operation) but fails to disclose whether existing labels are replaced or merged, what permissions are needed, rate limits, or how errors are handled. The single sentence provides minimal behavioral insight.

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?

Description is concise but overly minimal. It is front-loaded with the purpose, but lacks structure or additional details that would make it more helpful. A few more sentences could provide essential context without sacrificing conciseness.

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 no output schema, no annotations, and 0% schema coverage, the description is severely incomplete. It does not explain return values, side effects (e.g., idempotency), or how the tool integrates with other repository operations. Agent cannot reliably invoke the tool without missing crucial information.

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 coverage is 0% (no descriptions in schema), yet description does not explain any parameters (owner, repo, labels with fields). Agent cannot infer the purpose of each parameter from the description alone. This is a critical gap.

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 states 'Create labels on a repository for organization', clearly identifying the verb (create) and resource (labels on a repository). It distinguishes from sibling tools like add_repository_topics (adds topics) and repository management actions (archive, delete, etc.), but lacks specificity about the exact effect (e.g., whether it replaces or appends).

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 versus alternatives (e.g., add_repository_topics, update_repository). No prerequisites, restrictions, or context provided. Agent would have to infer usage from the name alone.

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