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

With no annotations, the description carries the full burden and does well: it discloses sorting (cheapest first), deduplication (one offer per panel), normalization (US dollars per 1,000), and returned fields (panel, Trust Score, links). It omits auth/rate-limit or result-count behavior and never explicitly states this is a read-only lookup, which keeps it from a 5.

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?

One dense, front-loaded sentence carries the operation, aggregation semantics, and output shape, followed by a short usage sentence. Every clause adds information, though the first sentence is long enough that it reads as slightly packed rather than crisp.

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 6-parameter tool with no annotations and no output schema, the description covers return content, ordering, currency normalization, and all optional filters. The remaining gap is the 'limit' parameter's default and cap, which the agent must read from the schema.

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 only 33%, so the description must compensate, and it does: it enumerates valid 'kind' values (followers, likes, views, comments, subscribers, members, shares, live) and explains the three boolean filters (refill, real-user, non-drop). It does not clarify the 'limit' parameter (default 5, max 10) or the platform key vocabulary beyond what the schema already gives.

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 operation on a specific resource: finding the cheapest offers of one service across all panels in the catalog, with the aggregation rules (one offer per panel, cheapest first). It is clearly distinguishable from siblings like list_services (all services) and search_panels (panels, not offers). An agent can select it without opening the schema.

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 concrete invocation contexts ('where to buy cheap Instagram followers', 'cheapest Telegram members'), which is strong positive guidance. It does not, however, name a competing sibling or state when NOT to use it (e.g., vs list_services for browsing), so it stops short of full alternative routing.

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