kfc_stores

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

With no annotations, the description carries the full burden of behavioral disclosure, and it excels. It explains the mandatory filter requirement, the exclusion of unfiltered enumeration, and the behavior of appear_in_store_results (default true) in excluding internal/test records, even noting it was 'confirmed live' that a raw filter can return non-orderable administrative entries. It also enumerates the exact fields returned for each restaurant (store number, address, coordinates, phone, online ordering status, timezone), providing comprehensive transparency about what the tool does and its edge cases.

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?

The description is informative but somewhat verbose and redundant. The first two sentences essentially repeat the same information ('Search KFC restaurants by...' and 'Returns KFC restaurants matching...'). It could be more concise by merging these. The description is front-loaded with the purpose, which is good, but the redundancy adds unnecessary length. It could be tightened without losing any key details.

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?

Given there is no output schema, the description compensates by detailing the return fields (store number, address, coordinates, phone, online order status, timezone). It also explains the filter requirement and the appear_in_store_results behavior, which are critical for correct usage. However, it doesn't explicitly describe pagination behavior beyond the max_results parameter in the schema, or error cases. It's quite complete for a tool with 9 parameters and no output 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%, so the baseline is 3. The description adds minimal value beyond the schema: it repeats the appear_in_store_results default and adds contextual detail about excluding internal records, but the schema already explains this parameter. The description doesn't add any new semantic meaning to the other parameters (city, state, postal_code, name, franchise_code, store_number, max_results, sort) that isn't already in their schema descriptions.

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 clearly states the tool's purpose: 'Search KFC restaurants by city, state, postal code, name, franchise code, or store number.' This is a specific verb (search) and resource (KFC restaurants) with clear filter criteria. It distinguishes from siblings like kfc_store (which presumably retrieves a single store) and kfc_nearby (which likely uses proximity) by listing searchable fields, even though it doesn't explicitly name those siblings.

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 provides a key usage guideline: 'At least one filter is required -- an unfiltered call would enumerate every US restaurant in one response, which this endpoint intentionally does not expose.' This is useful but doesn't explicitly advise when to use this tool versus alternatives like kfc_nearby or kfc_store. It mentions that the store number can be used with /kfc/menu and /kfc/promotions, but not the conditions for choosing this search over other store-related tools.

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