List Space Labels

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

The description adds minimal behavioral context beyond the annotations. It mentions the space scope and parameters but omits return format, pagination behavior, or any caveats. Given readOnlyHint=true and destructiveHint=false are already present, the description's contribution is limited.

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?

The description is concise and front-loaded with the core purpose, followed by a compact argument list. No fluff or redundant explanations, and the argument list is useful given the schema lacks descriptions.

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?

The tool has no output schema, so the description should explain return values and pagination details, but it doesn't. An agent cannot infer the response shape, sort options, or how to use the cursor, making the description incomplete for effective invocation.

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?

With 0% schema description coverage, the description must compensate for parameter meaning. It does provide terse definitions for each parameter, but some are nearly tautological ('sort: Sort field', 'space_id: Space ID'). 'prefix: Filter by label prefix' and 'cursor: Pagination cursor' add actionable semantics, though not deeply detailed.

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 clearly states the tool lists labels used across a space, providing a specific verb and resource. However, it does not differentiate from sibling tools like list_labels or get_space_content_labels, which could confuse an agent about which tool to choose.

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 provides no guidance on when to use this tool versus alternatives. It lacks any mention of alternative tools, exclusions, or preconditions, leaving the agent without direction on selection.

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