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 real behavioral context beyond that: prices are in Colombian pesos and products carry priced SKU variants across size, dough, crust and sauce. It does not mention pagination or response size (though an output schema exists).

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 sentences, no filler. The identity/currency/scope is front-loaded and the sibling differentiation is placed last, which is exactly the order an agent needs to decide relevance before reading the schema.

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, return format need not be explained, and both parameters are documented. The description covers market scope, currency, and content structure, leaving only minor gaps like result volume or whether the menu is location-independent.

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 both optional parameters (category filter and include_variants) are fully documented in the schema. The description's mention of 'priced SKU variants across size, dough, crust and sauce' loosely corresponds to include_variants but adds no syntax or default detail beyond the schema, 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?

States a specific resource (Papa John's Colombia priced menu) with scope markers: country (Colombia) and currency (Colombian pesos). It also explicitly differentiates from the sibling papajohns_intl_menu by noting Colombia runs a separate platform from the six markets behind the international tool.

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 final sentence effectively routes the agent: use this for Colombia, not the international menu tool, because they are separate platforms. It's clear context for selection but stops short of explicitly naming the alternative tool or stating exclusion conditions for the other country menus (El Salvador, Peru, Poland, Russia, India).

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