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

With no annotations, the description does add real behavioral context: it runs under the caller's OpenAny gateway credentials, and charges/authorization are gateway-determined. However, the cost disclosure is generic (it does not say what a search actually costs or how quotas behave), and it says nothing about the response payload or how reveal/enrich works relative to this call.

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?

Front-loaded with the core purpose in the first sentence, then two short caveats. Slight redundancy between 'Free search does not make enrich/reveal endpoints free' and 'Charges and authorization are determined by the gateway', but nothing is padding.

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 one-parameter POST search with a fully documented filter schema, the description covers what is searched, under whose credentials, and the billing/authorization caveat. Missing is any sense of the result shape, but with high schema coverage and a clarifying pagination note the gap is minor.

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% and the nested filter object already enumerates every supported key with caveats (e.g. the countries include-object being ignored). The description only restates the filter categories at a high level, so it adds little beyond the schema; baseline 3 applies.

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 and resource ('Search the Dropleads people database') plus the filter dimensions available (company, role, location, intent). The provider name distinguishes it from the many other people-search siblings (apollo_people_search, people_search_*), though it never explicitly tells the agent which of those to pick.

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 only implied: it is clear this is the tool to reach for when searching Dropleads people, and the note that free search does not extend to enrich/reveal endpoints hints at a cost boundary. There is no explicit when-to-use vs when-not, and no routing guidance against the ~20 sibling people-search/enrichment providers.

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