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 a useful list of returned fields, but with an output schema present that content is largely redundant, and it says nothing about authorization, rate limits, or behavior on a malformed path. Adequate but thin for the annotated baseline.

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, no filler. The richest information (the returned field list) is front-loaded, and the routing hint follows. Every clause earns its place.

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 output schema present, a 100%-covered single-parameter schema, and annotations covering the read-only/open-world profile, the description carries everything an agent needs: what it returns and which sibling to use instead when it lacks a path.

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% - the single 'path' parameter's origin (a 'locations' section 'store' path from GET /sonic/sitemap) is fully documented in the schema. The description adds no syntax, format, or lookup guidance beyond that, so the baseline of 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?

The description opens with a specific verb (Fetch) and resource (a Sonic Drive-In restaurant), then enumerates the exact payload fields (address, phone, coordinates, hours by fulfillment channel, amenities, delivery links). It is clearly distinguishable from sibling discovery tools such as sonic_locations or sonic_directory, which the description names explicitly.

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?

The second sentence routes the agent away from this tool for discovery: 'Use sonic_locations or sonic_directory to find stores.' That is an explicit alternative-naming, but the description never states the positive precondition for calling this tool - that you must already hold a sitemap-derived path - leaving that condition to the schema.

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