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

No annotations are provided, so the description carries the full burden. It correctly indicates a read operation ('List'), but lacks details on pagination, ordering, or potential edge cases (e.g., empty list). For a simple parameterless tool, this is adequate but not exhaustive.

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 wasted words. The first sentence front-loads the core purpose, and the second adds practical guidance. 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?

The tool is simple (no parameters, no output schema, no annotations). The description explains what it does and why it's useful (to obtain shop_id for create_order). It could be slightly more explicit about the return format (e.g., 'returns a list of shops with their IDs'), but it is substantially complete for the tool's complexity.

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 input schema already covers everything. Per the rubric, 0 parameters yields a baseline of 4. The description adds no parameter information, which is appropriate since there are none to describe.

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?

Description clearly states 'List the shops on YOUR ProShip account', using a specific verb and resource. It distinguishes itself from sibling tools (which are mostly order-related) by focusing on shops, and provides additional context by mentioning the shop_id's use in create_order.

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 implies the tool is for listing the user's shops and hints at downstream usage ('Use the shop_id with create_order'). However, it does not explicitly state when to use this tool versus alternatives, though no sibling tools exist for listing shops, so the context is clear enough.

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