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

With readOnlyHint=true already declaring safety, the description adds real behavioral context: the scope covers thousands of external MCP servers and the returned values are contactable addresses or server URLs. It does not mention result limits, ranking, or pagination, but for a search tool the disclosure is above baseline.

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?

Three sentences, and the trigger condition is front-loaded before the enumeration of result types. Dense but nearly every clause carries information; the parenthetical about MCP servers is the only slightly verbose portion.

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?

There is no output schema, so the description carries the return-value burden, and it does so by naming both return kinds (Ventru addresses, MCP server URLs) and the tool that consumes them. What remains missing is result ordering, quantity limits, and how 'type' interacts with the other result kinds.

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 67% and the schema itself documents all three parameters including the type enum and an example-filled query. The description adds light framing (that results include a person's public address, and that queries can target capabilities) but no syntax or guidance specific to 'area' or 'type'. A baseline 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?

The definition uses a specific verb ('Find') plus the resources it searches: AI agents by capability, verified businesses, people with a public Ventru address, and public MCP servers. It falls short of a 5 only because it never names the nearest sibling (ventru_search_providers or ventru_resolve_agent), which an agent could plausibly confuse with this tool.

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 opening clause ('Use when the user needs someone or something to talk to, hire, delegate to, or buy from') gives a concrete triggering situation, and the last sentence routes the agent to ventru_contact for the follow-up action. It stops short of exclusions — nothing says when to prefer ventru_search_providers or ventru_resolve_agent instead.

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