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

Adds useful behavior beyond the readOnlyHint/openWorldHint annotations: results are filtered to unseen leads by default and empty searches are not billed. However, it says nothing about result format, latency, plan limits beyond the count cap, or what 'proof' actually includes, so behavioral coverage is partial.

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 resource and purpose, and the operationally important clauses (new-leads default, unbilled empty search) are near the end but short. The long persona enumeration is mildly padded, yet each sentence carries information.

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?

With no output schema and only three parameters, the description supplies enough to call the tool correctly and set expectations about filtering and billing. Missing detail about returned fields/contact formats is acceptable since the prompt-style query does the heavy lifting.

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%, so the baseline is 3; the schema already explains count (plan caps), query examples, and include_seen. The description only reinforces the default-new-leads behavior behind include_seen and adds no syntax or formatting detail beyond the schema.

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 concrete verb+resource ('Find Web3 people, projects and Telegram channels') and enumerates the target segments (BD, founders, KOLs, VCs). It is clear what the tool retrieves, though the list of personas makes the opening sentence diffuse rather than sharp. No siblings exist to differentiate from.

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?

Gives actionable invocation guidance ('Describe who you need in plain English') and states the default scoping behavior (only new leads). It does not state exclusions or when NOT to use it, but with no sibling tools the main usage signal needed is present.

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