List storefront categories

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real behavioral context beyond it: an API key is required, the dataset is large (~7,000 entries), and the default category used by create_deal is Miscellaneous. It stops short of describing pagination or ordering behavior.

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?

Three short, front-loaded sentences with no filler; the core action leads. It loses a point because the vague 'for categoryId (about 7,000)' phrasing spends its brevity on something an agent can't act on.

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 read-only list tool with no output schema, the description covers auth requirements, scale, filtering, and a cross-reference to create_deal's default. The main omission is the 'max' parameter and result-set/pagination behavior, but overall it is adequate to call the tool correctly.

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?

Schema coverage is 0%, so the description must compensate for both parameters. It partially does for nameContains ('Pass nameContains to filter') but gives no substring/case semantics, and it never explains the 'max' parameter or its 1-500 bound. Real value added, but incomplete against a 0% coverage schema.

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 clear verb+resource: 'List storefront categories', which is distinct from siblings like get_deal/search_deals. However, 'for categoryId (about 7,000)' is confusing since no categoryId parameter exists, muddying what the tool actually returns. The core purpose is still recoverable.

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?

Gives implied usage ('Pass nameContains to filter') and useful cross-tool context ('Default used by create_deal is Miscellaneous'), which hints at when an agent would reach for it. But it names no alternative and gives no when-not guidance, so routing vs. siblings is left to inference.

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