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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds meaningful behavioral context beyond those: it returns no purchase action and only provider or CardDeals checkout links. This clarifies expected output behavior and non-transactionality without contradicting the annotations.

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 compact and front-loaded. The first sentence states the core use case, followed by supported inputs, an exclusion, and return behavior. Every sentence adds necessary information with no filler.

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-parameter tool with full schema coverage, strong annotations, and an output schema, the description covers all essential aspects: when to use, what input forms are accepted, what not to use it for, and what the response will contain. Nothing critical 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 coverage is 100%, so the baseline is 3. The description adds value by giving a concrete example ('brand:starbucks') and clarifying accepted forms (brand slug, product ID, or exact brand name) beyond the schema's terse parameter description.

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 a specific verb ('get'), resource ('live deals for one gift-card brand'), and scope ('one exact gift-card brand'). It distinguishes itself from siblings by explicitly saying it is not for broad category discovery, so an agent can tell it apart from search-like tools.

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 gives an explicit when-to-use condition ('when the user asks for complete current provider details for one exact gift-card brand') and an explicit when-not-to-use condition ('Do not use it for broad category discovery'). However, it does not name the alternative tool to use for broad discovery, so the routing guidance is slightly less direct than it could be.

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