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 value by enumerating the returned fields, including time-sensitive content (fulfillment hours, today's flavor). It does not mention freshness/rate-limit behavior, but with annotations and an output schema present, this is acceptable context.

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 resource ('Culver's restaurant detail') and then lists contents. Compact with no filler, though the trailing enumeration is dense.

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 an output schema present, return format need not be explained, and the description still summarizes key fields including the daily-updated flavor. Annotations cover the safety profile and the single param is documented, so an agent has enough to call it correctly.

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?

There is one parameter with 100% schema description coverage, so the schema fully documents it (required, sourced from /culvers/directory). The description adds nothing beyond the schema, which is the correct baseline when structured data does the work.

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 names a specific resource (Culver's restaurant detail) and enumerates exactly what it returns (address, phone, coordinates, hours, handoff options, order link, flavor of the day). An agent can distinguish it from culvers_directory (a list) and culvers_menu, but the description itself never explicitly contrasts with those siblings.

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: a detail tool whose slug derives from the directory. The schema notes the slug comes from /culvers/directory, hinting at the workflow, but the description gives no explicit when-to-use or when-to-prefer-an-alternative guidance (e.g., directory vs store vs flavor).

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