Manage Labels

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and non-idempotent, so the safety profile is largely covered. The description adds the useful nuance that 'list' is a read operation while 'create' mutates, but says nothing about permissions, duplicate-label behavior, or whether create is safe to retry.

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, front-loaded with the capability and followed by the control-field hint. No wasted words, though the brevity comes partly at the cost of the missing parameter detail.

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?

With five parameters at 20% schema coverage, no output schema, and a dual-action tool, the description should map parameters to actions and hint at results (e.g., what a list returns). It omits all of that, so an agent must infer which fields matter for which action.

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 only 20%, so the description must carry the burden — but it only names the `action` field, which the schema already documents via enum and description. It never explains that `name`, `color`, and `description` apply to create, or that `limit` applies to list, leaving four of five parameters uninterpreted.

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?

States a concrete verb set and resource: 'create and list labels' for a repository, which is more specific than the generic name 'manage_labels'. It does not explicitly distinguish itself from the many sibling manage_* tools, but the label resource is distinct enough for selection.

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?

It tells the agent to use the `action` field to pick the operation, and the enum limits that to create/list. However, it gives no guidance on when to choose this tool over siblings, no prerequisites, and no explanation of when create vs list is appropriate beyond the obvious.

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