list_locations

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

No annotations provided, so description carries full disclosure burden. 'List all' implies comprehensiveness but doesn't clarify pagination behavior (despite schema params), return object structure, or permission scoping. Contains no contradictions but limited behavioral detail.

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 well-structured sentences with zero waste: first establishes purpose, second provides usage context. Appropriately sized for the tool's complexity.

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 simple 2-parameter pagination structure and lack of output schema, description adequately covers intent and usage context. Would benefit from describing what fields a location object contains to aid filtering decisions.

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 has 100% description coverage for both pagination parameters, establishing baseline 3. Description adds conceptual context that the output provides IDs for filtering, but doesn't augment parameter syntax or validation rules beyond the 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?

The description provides a specific verb ('List') + resource ('shop locations') + domain ('Shopmonkey'), clearly distinguishing it from sibling list tools like list_customers or list_orders by specifying the unique resource type.

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?

Excellent context on when to use ('multi-location shops') and concrete purpose ('identify location IDs for filtering other resources'). Lacks only explicit exclusions or alternatives for single-location scenarios.

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