list_stores

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

With no annotations, the description carries the burden of disclosing behavior. The verb 'list' implies a read-only operation with no side effects, but it doesn't explicitly state that it doesn't modify anything or require any special permissions. For a simple list operation, this is adequate but not thorough. A more explicit statement like 'Does not modify any data' would earn a 4.

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, no fluff. The core action is front-loaded, and the practical usage tip about IDs is included without verbosity. Every word earns its place.

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 list tool with no parameters and no output schema, the description is complete. It tells the agent what the tool returns (store IDs) and how to use them. The only minor gap is that it doesn't describe the format of the response or whether the list is sorted, but these are not critical for correct invocation.

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?

The tool has zero parameters, so the schema provides full coverage by definition. The description doesn't need to add parameter details. Baseline for 0 parameters is 4, and nothing detracts from that.

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 action ('List') and the resource ('the user's grocery stores'). It also explains the purpose of the returned IDs, distinguishing this from other list tools like list_grocery_categories. The verb+resource pattern is specific and 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?

The description explicitly tells the agent how to use the output: 'Use the ids as `store_id` when adding or re-filing shopping list items.' This is clear usage guidance. It doesn't mention alternatives because there are no sibling tools that list stores, so no exclusion is needed. Slight deduction for not explicitly stating when NOT to use it, but that's minor given the unique purpose.

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