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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is clear. The description adds what the output covers, but it does not disclose any behavioral caveats such as reliance on public web signals, data completeness, or how the multi-threading strategy is derived. No contradiction exists, but the description adds only modest behavioral context beyond annotations.

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?

A single, dense sentence that front-loads the core action and resource, then compactly lists the key outputs. Every part earns its place, with no filler or repeated schema content.

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?

Given an output schema, full parameter documentation, and read-only annotations, the description is largely sufficient for an agent to understand what will happen. The main gap is the lack of sibling differentiation and usage guidance, which matters in a crowded tool list, but the core invocation context is complete.

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 all seven parameters already have detailed, meaningful descriptions. The tool description adds no parameter-level semantics beyond naming the output categories, so the 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 description uses a specific verb ('Map') and a specific resource ('internal buying committee'), and enumerates the four seats plus deliverables (title patterns, pain points, objections, multi-threading strategy). It is clearly about buying-committee mapping, but it never distinguishes itself from sibling research tools like get_company_intelligence or get_deep_research, so it stops short of a 5.

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 description gives no guidance on when to use this tool versus alternatives, no exclusions, and no prerequisites. 'For an account' is only a scope statement, not a usage rule. The agent is left to infer that this is for account-level buying-committee research without knowing which sibling tool to prefer.

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