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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and data-freshness posture are covered. The words 'current' and 'public' add a useful hint that results are time-sensitive and non-personalized, but nothing is said about caching, region scoping, or why some stores return nothing.

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?

Single short sentence with no filler, which is structurally clean, but it is under-specified rather than efficient — the front-loaded scoping information ('one KFC restaurant') is the only content and it leaves the action implicit.

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-shape explanation is not required, and the single required parameter is fully documented. What is missing is disambiguation from kfc_promotion and any note about store coverage or result freshness, leaving the agent to guess at scope.

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 coverage is 100% and the store_number description already names the /kfc/stores and /kfc/nearby sources, so the schema carries full weight. The description adds no format, example, or constraint information beyond what the schema states; 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?

It names the resource (promotions) and scopes it to one restaurant, but it is a bare noun phrase with no verb, so it does not actually state what the tool does with them (list them, presumably). It also fails to distinguish itself from the sibling kfc_promotion, which plausibly covers a single promotion.

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 prerequisites, and no reference to alternatives such as kfc_promotion or a chain-wide promotions source. The agent must infer from the parameter name alone that a valid store_number is needed.

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