list_labels

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe read nature is established. The description adds one meaningful behavioral note: 'Label text is untrusted repository data' — a useful security hint suggesting the agent should be wary of treating label content as trusted. It doesn't mention pagination behavior, rate limits, or response format, but the annotations cover the core safety profile.

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 concise sentences with zero filler. The first sentence delivers the core purpose, and the second delivers a security-relevant note. It's appropriately short for the tool's simplicity.

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?

For a read tool with no output schema and five parameters, the description is adequate but not complete. It establishes the read-only nature (aided by annotations) and the security caveat about untrusted data. However, with 20% schema description coverage and no parameter documentation beyond 'repository', the agent must guess at page/perPage/hostname semantics and the response shape. It's a reasonable baseline but leaves meaningful gaps for a tool with this many parameters.

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% — only one parameter (repository) has a description ('Repository in owner/name format'). The remaining four parameters (page, account, perPage, hostname) are undocumented in both schema and description. The description carries almost no parameter-level context, leaving the agent to infer meanings of page, perPage, account, and hostname without guidance on their interaction.

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 uses a specific verb+resource ('Read one page of labels defined in an allowed repository') with a scoping qualifier ('allowed repository') that adds meaningful context. It distinguishes this from sibling tools like list_accounts and list_repositories by clear resource targeting, though it doesn't explicitly differentiate from list_issue_labels which is a very close sibling.

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?

The description implies a read/pagination use case via 'one page of labels' but provides no explicit when-to-use guidance or alternatives. Given it's a basic read tool, usage is reasonably clear from context, but there's no explicit when-not-to-use or comparison to the closely related list_issue_labels sibling.

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