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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-world profile is covered. The description adds only a list of returned fields, which largely duplicates the output schema, and says nothing extra about auth, rate limits, or ordering-link behavior. Some value, but no meaningful behavioral disclosure beyond structured fields.

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 identity leads and the field list follows. Slightly list-heavy but nothing that fails to earn its place.

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?

An output schema exists, so return values need not be spelled out, and annotations cover safety, making the description adequate for a detail tool. However it omits any hint that the required 'path' comes from the directory tool, leaving the agent's selection logic thin.

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 and schema description coverage is 100%, so the schema fully documents how to supply 'path'. The description adds no interpretation, format, or example for the parameter, so 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 resource (Papa John's store detail) and enumerates the fields it returns (address, phone, coordinates, hours, timezone, Place id, ordering link), which clearly marks it as a detail-fetch tool rather than a list/search tool. It does not explicitly contrast itself with siblings such as papajohns_directory or papajohns_nearby, but the field list implies the distinction.

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?

The description gives no when-to-use or when-not-to-use guidance and never names the alternatives (papajohns_directory, papajohns_nearby) an agent would weigh against it. The only routing hint, how to obtain the store path, lives in the schema's parameter description rather than the tool description.

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