pizza_find_store

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only nature is known. The description adds context about the 'configured address' dependency and clarifies 'orders nothing', but these are somewhat redundant with annotations and do not disclose additional side effects or return format. This aligns with the calibration example where annotations cover safety and the description provides minimal extra behavioral context.

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 two short sentences, front-loaded with the action and purpose. It contains no unnecessary words, and the additional 'Read-only, orders nothing' is efficient, despite slight redundancy with annotations.

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 read-only tool with no parameters and no output schema, the description effectively covers the purpose, usage context, and safety. It specifies the output (store IDs) and the prerequisite (configured address), making it complete for first-time setup.

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 and the schema coverage is 100% vacuously. The description adds useful context about the config file and store_id output, but since there are no input parameters to clarify, the baseline for 0 params is 4.

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 'List the nearest Domino's stores for the configured address, with their store IDs', which includes a specific verb, resource, and scope. It also distinguishes its purpose by mentioning 'first-time setup' and 'pick the store_id', setting it apart from sibling tools like pizza_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?

It explicitly states when to use it ('for first-time setup') and provides an exclusion ('Read-only, orders nothing'), implying it is not for ordering. However, it does not name an alternative tool like pizza_order, so it lacks explicit alternatives.

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