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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the return-field inventory, but does not disclose anything beyond that (no rate limits, auth requirements, or freshness/staleness caveats). With annotations carrying the behavioral load, a 3 is appropriate.

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, zero waste. The field inventory is front-loaded so an agent can judge applicability before reaching the sibling-routing sentence, and every listed field earns its place by helping selection.

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?

A read-only, single-parameter fetch tool with an output schema and annotations covering the safety profile. The description does not need to explain return values (output schema exists) and it covers both what the tool returns and how to obtain the required path — complete for the 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?

Schema description coverage is 100% and the single 'path' parameter is fully documented in the schema itself ('Store path from a /wingstop/directory child with is_store true'). The description adds no additional syntax or format guidance, so the baseline 3 applies.

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?

States a specific verb (Fetch) and resource (a Wingstop store), then enumerates the exact fields returned (address, phone, coordinates, hours, service options, operating status, price tier). This is enough to distinguish it from wingstop_directory and wingstop_nearby, which locate stores rather than return one store's details.

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?

Explicitly names the two alternatives and the condition that selects them ('Use wingstop_directory or wingstop_nearby to find stores'), implying this tool is called once a store path is known. The schema reinforces this by requiring a path from a directory child. Nothing is left to inference.

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