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

Annotations already cover read-only and non-destructive behavior. The description adds only 'current' to suggest time-sensitive results, but it does not explain how 'best' is determined, whether results change over time, or any other behavioral details. It does not contradict 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 a single concise sentence with no filler words. It front-loads the action and resource, though it is so terse that some important context is missing.

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?

Despite having only two optional parameters and annotations, the tool competes with twelve sibling deal-related tools and outputs no schema. The description fails to explain what 'best' means, how results are ordered, or when this tool is preferable to get_latest_deals, get_trending_deals, or search_deals, so it is not complete enough for reliable selection.

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?

The input schema already describes both parameters with full coverage, including defaults and limits for 'limit' and the optional nature of 'category'. The description adds no parameter-level meaning, 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 states a clear action ('Get'), an object ('the best current deals'), and a source ('DealsPing'). However, 'best' is undefined and the description does not distinguish this tool from sibling tools like get_trending_deals, get_latest_deals, or search_deals, so it is clear but not differentiating.

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 use this tool versus its many siblings. The phrase 'best current deals' implies some selection ranking, but no criteria or comparison to alternatives is provided, leaving the agent to guess.

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