store_collection

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

With no annotations provided, the description carries the burden of explaining behavior. It discloses pagination behavior (has_more flag, offset/limit paging) and the result format (fields per row), which is useful. However, it does not mention whether any side effects occur, authentication requirements, or error conditions. The description is adequate but not rich.

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 concise and well-structured. It front-loads the purpose in the first sentence, then provides necessary parameter details in the following sentences. No unnecessary filler; every sentence adds value.

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?

Given the tool has 6 parameters and an output schema, the description covers the essential behavior: pagination, result fields, and required parameter values. However, it leaves out 'sort' semantics and possible hardware values. The output schema likely covers return structure, so the description is mostly complete but has minor gaps.

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 description coverage is 0%, so the description must compensate. It adds meaning for slug (examples), type_string (allowed values), limit/offset (pagination), and hardware (requested hardware flag), but does not explain the 'sort' parameter at all. Partial compensation with notable gaps.

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 function: 'List a named store collection, paginated, as compact summaries.' It specifies the resource (store collection) and provides concrete examples of slug values, which distinguishes it from sibling tools like store_search or store_category.

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 gives context on how to use the tool (e.g., valid slug examples and type_string values) and explains pagination, but it does not explicitly say when to use this tool over alternatives like store_search or store_developer. The usage is implied rather than contrasted with siblings.

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