list_labels

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered structurally and the description only needs to add context. It adds none: nothing about whether all labels are returned at once, how search matching works, or how many results to expect. The single clause about organising aliases is the only extra information.

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?

One short sentence with no filler and the core purpose front-loaded. Its brevity is appropriate for a simple list tool, though the same length could have been used to add when-to-use or matching detail instead.

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 one-optional-parameter read tool with annotations covering safety and no output schema, the description is roughly adequate but leaves real gaps: no mention of the search parameter's effect, result ordering, or whether an empty list is possible. Slightly more text would have made it complete.

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 100% and the single optional parameter is documented as "Search labels by name", so the baseline of 3 applies. The description does not add anything about matching semantics (substring vs exact) or default behaviour when the parameter is null.

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?

Specific verb+resource ("List the labels") plus a scoping note that labels organise aliases, so the agent knows what entity is returned. It stops short of distinguishing itself from siblings such as list_aliases or the create/delete_label tools, so it is clear but not differentiating.

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 versus alternatives (e.g., list_aliases when you want alias metadata, create_label when you need a new label). It also does not say when the optional search argument should be supplied rather than omitted.

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