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 the set of data categories returned (hours types, amenities, services), which is mild context, but says nothing about whether the path must be pre-resolved, whether results are cached, or any rate/authorization behavior.

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 with no filler — the resource is stated first followed by a compact field list. It is efficient, though the field enumeration is somewhat dense and the phrasing is a fragment rather than an actionable instruction.

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 the description need not explain return values, yet it spends its entire content enumerating them. It is adequate for a 1-parameter read-only detail tool, but omits the usage context (when to prefer it over directory/nearby siblings) that an agent would need to route 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?

Schema description coverage is 100% and the 'path' parameter is already thoroughly documented in the schema ('Store path from a /raisingcanes/directory child with is_store true'), which is the key semantic. The description adds no parameter-level meaning beyond that, 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?

The description names the resource ('Raising Cane's store detail') and enumerates the specific fields it exposes (address, phone, coordinates, hours, amenities, services), so an agent knows what it returns. However, it never states the action verb explicitly or distinguishes itself from the many sibling detail tools (raisingcanes_directory, raisingcanes_menu, raisingcanes_nearby), so it falls short of a 5.

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?

There is no when-to-use guidance at all. Nothing tells the agent to call this only after obtaining a store path, nor how it relates to raisingcanes_directory (which apparently supplies the path) or raisingcanes_nearby. The agent must infer usage entirely from the tool name and schema.

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