list_provider_capacity

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

The description does not disclose behavioral traits beyond the basic operation. No annotations are provided, so it should describe aspects like data freshness, pagination, or authentication requirements. It only says 'returns all provider-side listings' without further details.

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 two sentences, front-loaded with the main action. It is concise but could be slightly tighter by combining sentences. No superfluous information.

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 simple list tool with no parameters or output schema, the description provides minimal but adequate context. However, given the complexity of sibling tools and integration context, it could benefit from additional details about the return format or when to prefer this over 'find_provider_capacity'.

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?

There are no parameters, and schema coverage is 100% (empty). The baseline for 0 params is 4; the description does not need to explain parameters. It adds no parameter info, which is acceptable.

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 printers registered with connected provider integrations, and distinguishes it from siblings like 'find_provider_capacity' (targeted search) and 'sync_provider_capacity' (sync operation). The verb 'list' is specific and unambiguous.

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 explicit guidance on when to use this tool versus alternatives. The description does not indicate prerequisites, when not to use it, or how it compares to similar tools like 'find_provider_capacity' or 'sync_provider_capacity'.

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