whataburger_store

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

With no annotations, the description fully discloses behavior: returns specific data, explains that all page paths describe the same store and the response's path field is canonical, notes the 404 error case, and states the menu site is not automatable so this family is locator-only. No contradictions.

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?

Description is long but dense with essential information, front-loaded with the purpose, then details. It's slightly verbose but every sentence adds value; structure is logical and readable.

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 single-store detail tool with no output schema, the description covers return contents, input source, error behavior, and limitations (no menu). It is sufficiently complete for an agent to call correctly without additional context.

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 single 'path' parameter is well-described in the schema (100% coverage), and the description adds extra semantics: paths come from /whataburger/sitemap, and the distinction between canonical/curbside/delivery paths is clarified. Adds value beyond the schema.

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?

Clearly states 'Get one Whataburger store's detail' with a specific verb and resource, and enumerates the exact fields returned (address, coordinates, phone, hours, services, per-channel breakdown). Differentiates from sibling tools like whataburger_sitemap by explicitly targeting a single store detail.

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?

Provides clear context: store paths come from the sitemap endpoint, and warns that directory paths return 404. Implies the workflow (fetch sitemap, then use a path), but does not explicitly name alternative tools for listing or searching, though the context makes it obvious.

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