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

Annotations already declare readOnlyHint=true, and the description only restates read-only behavior via 'GET /shared_labels'. It adds no context on pagination limits, rate limits, ordering, or what the returned labels contain. The endpoint mapping is the only marginal addition beyond annotations.

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, nothing redundant, with the core action front-loaded and the supporting API detail trailing. Every element earns its place.

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 zero-required-param, read-only list tool with 100% schema description coverage and no output schema, the description is nearly sufficient. The main omission is any note on pagination behavior or result shape, but the schema carries most of that burden.

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?

All three parameters (limit, offset, organization) are fully documented in the schema, so the baseline is 3. The description adds nothing about parameter semantics — no explanation of pagination defaults or organization filtering behavior beyond what the schema already states.

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 specific verb and resource ('List shared labels') and clarifies the ambiguous term with a parenthetical ('team-shared folders/tags'), plus the backing API call. No sibling in the list overlaps with labels, so explicit differentiation isn't required, but it also doesn't position itself against nearby list tools.

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?

There is no when-to-use guidance, no prerequisite (e.g., auth/organization scoping), and no mention of alternatives such as other list endpoints. The verb 'list' implies retrieval, but nothing tells the agent under what circumstances to pick this tool.

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