chromewebstore_collection

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

No annotations are provided, so the description carries full burden. It describes the basic behavior (returns item cards, uses slug, defaults) but lacks disclosure on safety (read-only vs. destructive), rate limits, or authentication requirements. For a simple listing tool, the transparency is adequate but not thorough.

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?

Two sentences: first states purpose and output, second gives examples and defaults. Every sentence is informative, no wasted words. Front-loaded with the key action.

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 listing tool with full schema coverage and no output schema, the description covers the essential aspects: what it does, how to find slugs, and default parameters. It could mention the structure of 'item cards' or if pagination is involved, but it is sufficiently complete for an agent to use.

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 100% with all parameters described. The description adds significant value beyond the schema by explaining the 'collection' parameter as a slug, providing example slugs, and clarifying default values for 'num', 'country', and 'lang'. It also points to another endpoint for known slugs.

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 'List items in a curated Chrome Web Store collection' and specifies that it returns item cards for a given slug. It includes examples of slugs like 'editors_picks_extensions', making the resource and action 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?

Provides clear guidance on how to find collection slugs by referencing '/chromewebstore/categories'. States defaults for parameters, but does not explicitly mention when not to use this tool versus other similar tools like chromewebstore_search.

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