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

Annotations already declare readOnlyHint and non-destructive, so the safety profile is covered; the description adds genuine behavioral context beyond that — that titles yield hypotheses rather than confirmed authority, that sector-specific roles and questions appear only when inputs name a supported sector, that business_model is inferred from other inputs when omitted, and that confirmed_budget_owner overrides candidate ordering. It does not disclose limits of the sector library or what happens with an unsupported sector, which keeps it off a 5.

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 decision it supports, then a compact input clause, then the output inventory — a sensible order with little waste. The middle sentence is long and carries several nested enumerations, which slightly hurts scannability but every clause conveys real 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?

There is no output schema, and the description compensates by describing the returned artifacts in prose (role placement, concerns, message prompts, influence map, discovery questions, sector augmentation). Combined with full schema coverage and read-only annotations, an agent has everything needed to invoke it correctly and interpret the result.

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 description earns above that by clarifying the dependency logic between parameters (business_model read from other inputs, confirmed_budget_owner overriding candidate ordering) and by signaling that a 'supported sector' concept gates part of the output. Those are cross-parameter behaviors the per-property schema text cannot express.

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 opening sentence states a specific decision outcome: 'Helps you decide who else must agree before a deal can close.' It then enumerates exactly what the tool produces — a buying group map with roles placed by title, per-role concerns and message prompts, an influence map, and discovery questions — which is concrete enough that an agent can tell this apart from the ICP and TAM/SAM siblings in the same family.

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 clear activation context ('before a deal can close' with 'what you sell, the deal size, the company size, your champion and any stakeholders you know'), which is effectively an input checklist-plus-timing signal. It stops short of naming an alternative tool or stating when not to use it, so there is no explicit routing guidance against the sibling ICP tools.

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