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

Annotations already mark it read-only, idempotent, and non-destructive. The description adds meaningful context beyond that: data source (DOL Form 5500), scale (58,000+ brokers), ranking criteria (filings carried), and the fact that no API key is required. This enriches the agent's understanding without contradicting annotations.

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 description is a single well-structured sentence that front-loads the core purpose, then adds target audience and a practical note (no API key). It is concise while including essential context, though it could trim a few words without loss.

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 simple read-only directory tool with three optional parameters and no output schema, the description covers the data content, source, ranking, and audience. It doesn't need to explain return values since there's no output schema, and pagination is already in the schema via the page parameter. It is sufficiently complete.

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 100% – each parameter (q, page, state) is already documented. The description adds no param-specific guidance beyond the schema, so a baseline of 3 is appropriate.

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 resource (benefits brokers from DOL Form 5500 Schedule A Part 1) with clear detail on ranking and metrics. The sibling tools focus on other data domains (benefit plans, lenders, money movement, etc.), so this tool is easily distinguished without needing to open its 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?

The description gives explicit use cases (carriers, broker M&A, benefits-tech sellers, brokers scouting competitors) that make the intended context clear. It does not name specific sibling tools or state when not to use it, but the purpose is so domain-specific that the usage is effectively implied.

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