deals_v2

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

With no annotations, the description carries the burden. It discloses the HTTP method (GET), the API key requirement, and that no required params are needed. It does not mention return format, pagination, or rate limits, but for a read-only list endpoint the disclosed details are reasonably helpful.

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 short and front-loaded with the endpoint. The three sentences each carry useful information: the endpoint, the lack of required params, and the API key plus guide reference. The listing of multiple environment variable names is a bit repetitive but tolerable.

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?

This is a simple GET list tool with no required parameters and no output schema. The description provides enough to make a basic call (auth, no required params) and points to a guide for full details, but it does not explain what the response contains or any optional filters, so completeness is adequate but not rich.

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 high (100%) with generic envelope parameters already described. The description adds that no required parameters exist, which is useful, but it does not enumerate any optional query parameters specific to the deals endpoint, so it adds only marginal value beyond the schema.

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 identifies the endpoint as '[GET] /deals/v2' and labels it 'Deals List', specifying a verb and resource. However, it does not differentiate this from sibling tools like 'games_bundles_v2' or 'games_prices_v3', so it is clear but not fully distinguishing.

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 states that no additional required parameters exist and that an API key is needed, along with a pointer to the 'itad://guide/calling' resource for full instructions. It does not explain when to prefer this over alternatives or provide exclusions, so guidance is present but limited.

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