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 still adds value by clarifying that the input is a directory path (a pointer, not a free-text query) and summarizing the profile contents. It omits any auth/rate-limit/no-result behavior, so it falls short of a 5.

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 action and followed by the navigation hint. The enumerated return fields partially duplicate the output schema, adding slight redundancy, but overall it is efficient.

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?

For a single-pointer read with an output schema and read-only annotations, the description covers the essential context: what it returns, what input it needs, and where to get that input. Return values needn't be restated given the output schema, so nothing critical is 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% and the `path` parameter is fully documented in the schema (including the is_store true requirement). The description only restates that the path comes from directory/nearby, adding little beyond what the schema already provides. 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 (Fetch) and resource (one Papa John's store profile), scoped to a single store via directory path. It enumerates the returned content (address, phone, coordinates, hours, timezone, Place ID, order link), making it easy to distinguish from the sibling finder tools.

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 the agent: 'Use papajohns_directory or papajohns_nearby to find store paths.' This names both alternatives and the condition (need a path) that selects them, leaving nothing to inference.

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