List location discounts

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is well covered. The description adds meaningful context beyond those annotations by disclosing the API key requirement and that the API verifies key access to the requested location, which is directly useful for invocation planning.

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 with no filler: the core behavior is front-loaded, and the authentication requirement follows immediately. Every word contributes to helping the agent understand what the tool does and what is needed to call it.

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-optional-parameter read-only tool with a rich annotation set and an output schema, the description is complete. It covers the essential invocation context (API key requirement, authorization check, location scoping) without needing to explain return values because the output schema exists.

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 locationId parameter already includes a clear 'Omit to use CRAVEUP_LOCATION_ID' explanation. The description reinforces that the operation targets 'one authorized location' but adds no new parameter-level semantics beyond what the schema provides, so the baseline of 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 uses a specific verb ('List') and resource ('every discount configured for one authorized location'), making the tool's purpose immediately clear. It also distinguishes itself from write-sibling create_order_discount by focusing on enumeration, and from list_locations by targeting discounts rather than locations.

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 clear context: this tool lists discounts for a single authorized location and requires a Crave merchant API key. It does not explicitly name alternatives or when-not-to-use conditions, so it falls short of a 5, but the purpose is specific enough for an agent to route correctly.

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