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

Annotations already cover readOnly/idempotent/openWorld safety, but the description adds real behavioral context beyond them: default responses are compact summaries, pagination must be followed, and provider text is untrusted (a valuable security caveat). It stops short of describing rate limits, auth scope, or response shape.

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?

Dense and front-loaded: the core default behavior comes first, then the two expansion modes, then pagination and the trust warning. Telegraphic phrasing is efficient though slightly terse in places.

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?

No output schema exists, so the description must convey return behavior; it does explain the compact-by-default vs verbose distinction and pagination, but omits semantics for api_key and provider_id and any input constraints. Adequate but with clear gaps for a 7-parameter 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 0% schema description coverage, the description must carry parameter meaning, and it explains q (filters names/descriptions), tool_name (returns that tool's schema), and verbose (full pages). It leaves limit, offset, provider_id, and api_key entirely unspecified, so coverage is partial.

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 specific verb (Find) and resource (reviewed provider tools) with a clear scope qualifier ('reviewed'). It distinguishes itself from siblings by being the provider-tool listing endpoint, though it does not explicitly name any alternative tool, keeping it short of a 5.

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?

Offers mode-selection guidance: use tool_name for a schema, verbose=true for full pages, q for filtering, and follow pagination. However, it never says when to prefer this tool over siblings like list_research_connectors or search_information, so the guidance is implied rather than explicit.

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