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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered externally. The description adds genuinely useful context about the depth of the return (per-choice price and calorie deltas, allergen flags), but since an output schema exists this is largely restating return content rather than disclosing operational behavior like pagination or auth.

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?

A single front-loaded sentence that leads with the scope ('One Shake Shack location's full menu') and then enumerates contents. It is long but every clause carries information; minor length could be trimmed without loss.

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?

With a full output schema and read-only/open-world annotations, the description need only frame what the tool returns and for which scope, which it does well. It lacks explicit guidance on sourcing the location_id and has no sibling routing, leaving a small gap.

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 location_id parameter is fully documented in the schema, including its source endpoint. The description adds no syntax, format, or range detail beyond that, so the baseline 3 for schema-does-the-work 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 resource (one location's full menu) and enumerates the retrieved content (categories, products, calories, allergens, customization tree), so the agent knows exactly what this returns. It does not name or differentiate against siblings such as shakeshack_store or shakeshack_locations, so it stops short of a 5.

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?

Usage is only implied: the 'one location' framing and the required location_id suggest this is the drill-down after locating a store, but the description never states when to use this vs alternatives or any prerequisites. The 'Location id from /shakeshack/nearby' hint lives in the schema, not the description, so guidance here is thin.

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