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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful context beyond them: calories may be a single value or a real range, price is the live selling price, and availability is live — plus it disambiguates the id universe ('not a Yext entity id'), preventing a common wrong call.

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?

Front-loaded with purpose, then the field list, then the sibling contrast, then the id caveat — a logical order with no filler sentences. The enumeration of returned fields is partly redundant given an output schema exists, which is the only mild inefficiency.

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?

An output schema exists, so return values need no prose, and the description still supplies the scoping constraint, sibling contrast, live-data caveats, and id provenance an agent needs to call this correctly. Nothing material is missing for a single-required-param read tool.

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 coverage is 100% and the single parameter is documented there, so the baseline is 3. The description goes further by specifying the id's provenance chain (ordering-locations' locations[].id) and explicitly excluding the Yext entity id, which is semantic guidance the schema alone does not convey.

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+resource with scope ('One Five Guys restaurant's full priced menu exactly as the ordering platform sells it') and explicitly differentiates from the sibling fiveguys_menu, which it notes has no prices. An agent can route correctly without opening either schema.

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?

Names the alternative (fiveguys_menu) and the differentiating condition (prices vs. no prices), and directs the agent to fiveguys_ordering_locations to obtain the required id. It does not, however, define when a single-restaurant menu lookup is preferred over the broader ordering-locations or nearby flows.

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