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

With no annotations, the description carries the full burden. It usefully discloses the result ordering ('ranked by approvals') and that this is a PRO/subscriber-gated feature, hinting at the access_token requirement. It says nothing about read-only safety, result volume, pagination, or what happens with zero filters despite all parameters being optional.

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?

A single tight sentence with no waste, and the core capability is front-loaded before the audience note. The telegraphic 'PRO.' fragment is slightly cryptic but costs little space.

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 no-output-schema, no-annotation, all-optional search tool, the description covers what it returns conceptually (ranked sponsors) and who it's for. It stops short of describing response fields or behavior with no filters, but the essentials for correct invocation are largely present.

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 17%, so the description must compensate. It clarifies that 'naics' is an industry *prefix* and that state/city are filters, adding real meaning for three of six params. But limit, min_approvals, and the relationship between min_approvals and 'ranked by approvals' are left unexplained.

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 the resource (H-1B sponsors), the filter axes (state, city, NAICS prefix), and the ranking (by approvals), so an agent knows this is a ranked sponsor lookup. It doesn't explicitly distinguish itself from employer_detail or h1b_check, but 'lead lists' implies a broad discovery search versus a single-record lookup.

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 audience framing ('lead lists for recruiters, immigration lawyers and job-seekers') implies an exploratory/browse use case, which tacitly points away from employer_detail. However, there is no explicit when-to-use or when-not statement naming the sibling tools.

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