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

Annotations already mark it readOnly/idempotent/non-destructive/open-world, but the description adds real behavioral context: one page of up to 10 results, cursor-based continuation via nextCursor, that listings may be invited-only, that price/storefront slug/purchase permission are omitted, and that provider text is untrusted. The untrusted-data warning is especially valuable; only rate limits/auth are unaddressed.

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?

Three tight sentences, front-loaded with purpose, then pagination mechanics, then the caveats about excluded fields and untrusted content. Nothing is wasted, though the reference to 'nextCursor' is slightly cryptic before the output is seen.

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?

An output schema exists, so return values need not be described, and the description covers the key usage caveats (pagination, invited-only listings, omitted fields, untrusted text). It falls short only on explaining the parameter surface, which is undocumented in both schema and description.

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 0% and there are 4 top-level parameters with a nested query object. The description clarifies the 10-item page size and the nextCursor→cursor hand-off, but leaves search, query, after, and definitionDigest entirely undocumented, so it only partially compensates for the coverage gap.

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?

Specifies a clear verb and resource ("Find public Voidpay service descriptions"), so an agent knows this browses the service catalog. It does not, however, differentiate itself from the sibling tools (voidpay_storefront, voidpay_status, voidpay_checkout_link), leaving the distinction to inference.

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?

The description offers operational guidance about search and pagination but never states when to use this tool versus its siblings, nor any exclusions. There is no explicit 'use this when... / use X instead' routing.

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