get_discount

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 useful behavioral context beyond annotations: the result for an unknown id and the budget-offer prerequisite. It does not, however, explain the odd confirm parameter that the schema says is ignored when reading.

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 four short sentences with no waste. It front-loads what the tool does, then adds lookup guidance, read-only behavior, and the prerequisite in a logical order.

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 values need not be documented. The description covers the required id, the read-only guarantee, not-found handling, the list_discounts lookup path, and the feature prerequisite. Nothing essential for calling this read tool is missing.

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 schema already documents both parameters. The description only restates that the id identifies the discount and says nothing about the confirm parameter. Baseline 3 is appropriate when the schema fully carries parameter semantics.

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 states a specific verb and resource ("Read one discount by its identifier") and enumerates the fields returned (name, amount, project/task). It clearly distinguishes this single-object read from list_discounts and from create/update/delete_discount 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?

It explicitly routes the agent to list_discounts to obtain the id first, states the read-only nature, describes the not-found behavior for unknown ids, and names the prerequisite feature (Gryzzly's budget offer). This covers when to use the tool and the key prerequisites.

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