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

With readOnlyHint=true and destructiveHint=false, the safety profile is already disclosed. The description adds no behavioral detail such as dynamic ranking, time-sensitivity beyond the word 'currently', pagination, or rate limits. It does not contradict annotations, but it adds minimal value beyond them.

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 a single, front-loaded sentence with no filler words. It is efficient, though it could have used the space to provide sibling differentiation without becoming verbose.

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?

The description is minimally viable: it names the resource, annotations cover safety, and the schema covers parameters. However, it lacks a definition of 'trending', any return-format details (no output schema), and differentiation from the 12 sibling tools, leaving a notable gap for an agent selecting the right tool.

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%: the single optional limit parameter is fully documented in the input schema. The description adds no parameter context, but the schema carries the full burden, so the baseline 3 is appropriate.

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 clear action and resource: 'Get currently trending deals'. It is not a tautology and the resource is more specific than a generic 'Get deals'. However, it does not explicitly differentiate from sibling tools such as get_best_deals or get_latest_deals, so it falls short of a top score.

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?

There is no guidance on when to choose this tool over the many sibling deal-lookup tools. The description only says what it does, not when it should be used or what distinguishes trending from latest or best deals.

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