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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful context beyond them: alphabetical ordering, default 10 and maximum 20 results, 15-minute cursor reuse with the same filters, records changing between pages, locations as candidates rather than confirmed availability, and no filter relaxation on empty results.

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 definition is five tight sentences that front-load purpose and then add necessary operational caveats. Every sentence contributes useful scope, pagination, or filtering information without filler.

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?

Because an output schema exists, the description need not explain return values. It covers filtering, ordering, result limits, cursor freshness, location caveats, and empty-result semantics, which is complete enough for a read-only provider search 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?

With only 20% schema description coverage, the description compensates by explaining the query as literal name search, category filtering, exact provider-location key semantics, limit default and maximum, and cursor reuse constraints. It still omits category enum meanings and query length or pattern details that remain in the schema, but it adds substantial parameter meaning.

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 search verb and resource and scope: published Free and paid providers, filtered by literal name query, category, and exact provider-location key. It does not explicitly position itself against get_provider or compare_providers, so sibling differentiation is inferable rather than stated.

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: use this to search or discover providers, with notes that empty results never relax filters and cursor reuse requires the same filters. However, it gives no explicit when-to-use or when-not-use guidance and does not name an alternative tool.

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