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 behavioral value by specifying the record's content and temporal scope ('per-service availability/hours, and published storefront hours for the next week'), though it omits auth or rate-limit notes.

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 tight sentences, front-loaded with the core action and its output, followed by the sibling routing. No redundant or filler content.

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 covering safety, the description need not explain return values. It covers purpose, scope, and sibling alternatives for a single-parameter lookup; only explicit usage conditions and operational caveats are missing.

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%, so the single cafe_id parameter is already documented as 'Required. Panera cafe id, from /panera/locations.' The description only restates 'by cafe_id' and the discovery source, adding no syntax or format detail beyond the schema, so baseline 3 is 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 verb and resource: 'Fetch one Panera cafe profile record ... by cafe_id.' It enumerates the returned fields (location, phone, amenities, per-service availability/hours, published hours for the next week), so an agent immediately knows what it retrieves and how it differs from list/discovery 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?

It explicitly routes to alternatives: 'Use panera_locations to discover cafes, panera_geocode for address lookup, or panera_time_slots for ordering windows.' This gives clear selection context, though it never states the inverse condition (i.e., 'call this only when you already hold a cafe_id'), leaving that to inference.

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