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 only characterizes the shape of returned content, which the output schema already carries, and says nothing about auth requirements, rate limits, or failure modes. It adds little behavioral information beyond the 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 dense sentence, front-loaded with the resource name and then the payload contents. Nothing is redundant, though the trailing enumeration of return fields is somewhat heavy for a description whose return values are already schema-defined.

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, full parameter coverage, and read-only annotations, the description only needs to establish what the tool is for. It does that adequately, leaving the minor gap that the upstream source of offer_id is only discoverable via the schema.

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% for both required parameters, and the schema itself enumerates the allowed market values and documents that offer_id comes from the deals endpoint. The description adds no syntax or format detail 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 specific resource ('Papa John's offer composition for an international market') and enumerates what the composition contains: offer price, choice steps, and eligible products with surcharges and ingredient rules. It is clearly distinguishable from sibling tools like papajohns_intl_deals or papajohns_intl_product, though it does not explicitly contrast itself with them.

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, no mention of the upstream step that produces offer_id, and no exclusion of alternatives. The only routing hint ('An offer id from GET /papajohns/intl/deals') lives in the schema, not the description, so the description itself provides no usage context.

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