find_shop

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, covering safety and side effects. The description adds 'complete paginated' but does not detail pagination behavior (e.g., how to iterate) or other nuances, providing minimal incremental transparency.

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 a single sentence that conveys the core function and a sibling reference. It is concise and front-loaded, but could be slightly more structured (e.g., separating the sibling note). Overall efficient.

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 has an output schema (though not provided in input) and three parameters. The description indicates pagination and completeness, but lacks details on pagination mechanics, required parameter behavior, and error cases. It is adequate for a simple tool but not fully comprehensive.

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 only 33% (only 'item' has a description). The description does not explain the 'limit' or 'offset' parameters, and the schema's description of 'item' as 'Exact Wiki item name' is minimal. The description fails to add meaning beyond what the schema provides, leaving parameter usage ambiguous.

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 retrieves 'the complete paginated Old School RuneScape Wiki shop listing for an item', specifying the resource (shop listings) and verb (get). It distinguishes from the sibling 'get_item_sources' by calling it 'the bounded overview', indicating scope differentiation.

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 mentions 'get_item_sources is the bounded overview', providing a direct comparison to a sibling tool. However, it does not elaborate on when to avoid using this tool or specify prerequisites beyond item name matching.

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