list_commerce_tools

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

No annotations are provided, so the description must convey behavioral traits. It explicitly states 'Free — no payment is made,' which addresses cost concerns. The verb 'List' suggests a read-only operation, but it does not explicitly guarantee no side effects or disclose other behaviors like pagination. Still, the added cost info is valuable.

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-loads the core purpose, and includes useful additional detail without fluff. Each sentence serves a purpose.

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 parameterless listing tool, the description covers what is listed, what attributes are returned, and cost. Without an output schema, this is sufficient for an agent to understand what to expect. No further detail is necessary.

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?

The tool has zero parameters, so there is nothing to explain beyond the schema. The description adds context about what the listing includes, but parameter semantics are inherently covered by the empty schema, earning the baseline score for no parameters.

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's purpose: to list every commerce tool exposed by the server, including specific attributes (upstream service, price, payment rail). This distinguishes it from sibling tools which perform distinct actions like buying, pricing, or booking.

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 this tool is for enumerating available commerce tools, but it does not explicitly state when to prefer it over alternatives or mention any exclusions. It provides context about being free but lacks direct usage guidance relative to sibling tools.

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