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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description's added value is naming the returned fields, which is genuinely useful context, but it discloses no behavioral traits beyond that (no pagination, freshness, or 'today's flavors' timing caveats).

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, zero waste: the capability and its payload are front-loaded, and sibling routing follows. Nothing is redundant or padded.

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 and annotations carrying the safety profile, the description needn't explain returns yet does so helpfully. It is essentially complete for a one-param read tool, losing only a point for not stating the obvious slug-acquisition precondition.

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 slug parameter is documented in the schema as coming from /culvers/directory. The description adds no syntax or format detail beyond this, so the baseline 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?

States a specific verb ('Fetch') and resource (a Culver's restaurant) and enumerates exactly what comes back: address, phone, coordinates, fulfillment hours, handoff options, order link, today's flavors. This distinguishes it cleanly from culvers_directory, culvers_menu, and culvers_flavor.

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?

Explicitly routes to culvers_directory for finding restaurants and culvers_menu for food items, so the agent knows what this tool is not for. It stops short of stating the prerequisite (you need a slug obtained from the directory first), which is implied but not spelled out.

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