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

With no annotations, the description must carry behavioral load, and it does disclose the important cost model (free count, paid results) and that authorization/charges flow through the caller's OpenAny gateway credentials. It stops short of describing the response shape, failure modes, or any rate limits, leaving meaningful gaps for a data-billed API.

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?

Two short sentences, front-loaded with the purpose and followed by the credentials/billing caveat; nothing is wasted. The mid-sentence line break is cosmetic rather than harmful.

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 single-parameter counting tool it covers purpose and cost/auth, which is the core. However, the filter object is an untyped open object whose semantics depend on 'icypeas.people.search', a tool not present in the sibling list, so the agent has no resolvable path to learn the filter contract.

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 100%, and the schema itself already explains that the query object is 'identical filter object to icypeas.people.search', which is the most useful semantic hint. The description adds nothing about the query filter's fields or format beyond the schema, so the 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?

The description states a specific verb and output (a count of matching people) and a scope ('before you pay to read any of them'), which separates it from a paid people-search that returns records. It never names the paid sibling by tool name, so the distinction is implied rather than explicit.

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?

'Before you pay to read any of them' hints at a pre-flight sizing use case, so an agent can infer this is a cheap count check ahead of a paid search. There is no explicit when-to-use/when-not-to-use statement and no named alternative tool to call afterwards.

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