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

No annotations are provided, so the description carries the full burden. It usefully discloses return content — each result carries a Trust Score, reviews, and a link — but says nothing about rate limits, pagination behavior, auth needs, or result ordering.

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?

Two sentences, front-loaded with the resource scope followed by the filter mechanism. The category enumeration is dense but each item earns its place by defining coverage; nothing is redundant.

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 3-param search tool with no output schema and no annotations, the description covers what it searches, what it returns, and how to filter. The remaining gap — pagination via 'limit' and result ordering — is minor for a discovery 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 coverage is only 33% (only 'query' is documented in-schema), so the description is expected to compensate. 'Filter by category and name' does clarify the two filter fields, but the limit/pagination parameter is never addressed and no match semantics (exact vs contains) are added.

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?

States a clear verb (search/filter) and a specific, enumerated resource — panel scripts, payment gateways, hosting, domain registrars, SMS verification, proxies, VPN, engagement platforms — which cleanly delineates it from the panel- and service-specific siblings. No explicit naming of those siblings, but the enumeration makes the scope unambiguous.

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?

Usage is implied by the category list and the closing 'Filter by category and name,' so an agent can infer when to reach for this tool over search_panels/search_services. There is no explicit when-not or named alternative, leaving the routing to inference.

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