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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful output context (roles, priorities, outreach order, named people), but says nothing about sourcing, data freshness, or what 'plus any people named on the…' actually means, and it is truncated.

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?

The description is visibly truncated with an ellipsis and then repeats its opening clause verbatim, so it is neither cleanly front-loaded nor free of waste. The duplication and cutoff hurt rather than help the agent.

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 tool with a nested input object, no output schema, and a truncated description, critical information is missing — how the target company is supplied, what output format to expect, and what the trailing clause was going to say. An agent cannot be confident about correct invocation.

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?

There is a single nested 'input' object whose schema description is only a URL pointer, so the schema itself carries almost no semantic content. The description implies 'target company' as the unit of work but adds no format or structure details. Baseline 3 applies given nominal 100% coverage with no real enrichment.

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 names a specific verb and resource ('map the buying committee') and adds concrete detail about what it produces: target roles, their priorities, and outreach order. That distinguishes it from generic enrichment or contact-finding siblings, though it never names those siblings explicitly.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no alternatives named. With many adjacent siblings (b2b_account_brief, b2b_crm_enricher, b2b_outbound_engine, email_finder_scraper), the agent is left to guess which tool fits.

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