List product catalogs

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 without the description. The description adds nothing beyond that: no pagination behavior, no result count/ordering, no note on what is returned or whether an empty business yields an empty list.

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?

A single front-loaded sentence with zero wasted words. It errs on the thin side rather than being bloated, but structurally clean.

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-parameter read-only list tool with annotations covering safety and no output schema, the essentials are present. Still missing the provenance of business_id and any sense of return shape or pagination, so it is only minimally 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?

One parameter with 0% schema description coverage. The phrase 'of a business' loosely identifies business_id as the owning business, which is the only added meaning; no format, source, or example for the ID is given. Baseline 3 for a single self-describing parameter.

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 ('List') and resource ('product catalogs') and scopes it to a business, so it is distinguishable from the singular read sibling get_catalog. However, it does not name get_catalog or the create/update/delete catalog siblings to sharpen the boundary.

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 explicit when-to-use guidance or statement of prerequisites (e.g., that business_id must come from list_businesses). Usage is only implied by the verb 'List'. No alternatives are named despite the catalog family having get/create/update/delete variants.

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