list_locations

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List store locations' implies a read-only operation, but it doesn't specify whether this requires authentication, how results are returned (e.g., pagination details beyond the cursor parameter), rate limits, or any side effects. The description lacks critical behavioral context needed for safe and effective use.

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 extremely concise at three words, with zero wasted language. It's front-loaded with the core action ('List') and resource ('store locations'), making it easy to parse quickly. Every word earns its place by directly conveying the tool's function.

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 complexity (a listing operation with 2 parameters), no annotations, no output schema, and 50% schema coverage, the description is incomplete. It doesn't address return values, error conditions, or behavioral nuances. For a tool that likely returns structured location data, more context is needed to guide effective 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 description coverage is 50% (only 'limit' has a description, 'cursor' does not). The description 'List store locations' adds no parameter-specific information beyond what the schema provides. It doesn't explain what 'store locations' means in terms of data structure or how parameters interact with the listing. With partial schema coverage, the description fails to compensate for the undocumented 'cursor' 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?

The description 'List store locations' clearly states the verb ('List') and resource ('store locations'), making the basic purpose understandable. However, it doesn't distinguish this tool from other list tools on the server (like list_accounts, list_items, etc.) by specifying what makes 'store locations' unique or different from other listing operations.

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 provides no guidance on when to use this tool versus alternatives. There are multiple sibling tools (e.g., list_accounts, list_items) that perform similar listing operations, but the description doesn't explain when store locations should be listed instead of other entities, nor does it mention any prerequisites or contextual triggers for using this specific tool.

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