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. The description adds that the response contains a modifier tree and nutrition data, but with an output schema present this is largely a restatement of return contents rather than new behavioral context such as depth limits or size of the tree.

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 compact sentence with the resource named first and the notable return characteristics following. No filler, though it is terse enough that the sibling boundary is never addressed.

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, full schema description coverage, and annotations covering read-only/open-world behavior, the description supplies everything an agent needs to call this correctly: the resource, its required inputs' provenance, and the shape of the payoff.

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% for both parameters (category and item slugs with their source endpoints), so the schema carries the parameter burden. The description adds no syntax, format, or lookup guidance beyond what the schema already provides, making the baseline 3 appropriate.

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 (Culver's menu item full detail) and its distinctive content: a size/topping modifier tree with per-option calories and nutrition links. It's clear what the tool returns, but it never contrasts itself with the closely-named sibling culvers_menu, so the agent must infer the boundary.

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: it needs a category slug and item slug, which the schema itself documents as coming from /culvers/menu and /culvers/categories. There is no explicit statement of when to pick this over culvers_menu or other Culver's endpoints.

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