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

With no annotations provided, the description carries the burden of explaining behavior. It does disclose the core selection logic: peers run the item and the company does not, ranked by how many peers carry it. Still, it does not describe output shape, pagination, edge cases, or read/query limitations.

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 extremely concise: two sentences that immediately define what the tool returns and who it is for. Every phrase earns its place, and there is no redundant repetition of the tool name or schema.

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?

The description is adequate for a simple ranked-list tool and gives a clear use case, but it is not fully complete: with no output schema and no annotations, the agent still lacks a clear expectation of the returned record shape and the exact semantics of slug/limit.

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?

The schema has 0% description coverage and the description adds little parameter-level guidance. It relates 'this company' to the slug parameter only implicitly, and it does not explain how limit affects the ranked list or what slug values are acceptable.

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 clearly identifies the tool's output: it lists what the company's peers run that the company does not, ranked by peer adoption. It also adds a strong use-case framing: 'The opening list for a vendor selling into the account.' It is not a full 5 because it lacks an explicit imperative verb and does not distinguish this from sibling tools like company_gaps.

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 a clear audience and context: a vendor selling into the account should use this as the opening list. However, it provides no explicit when-not-to-use guidance or alternatives among the many sibling tools, so an agent must infer when this is preferred over similar company/peer/gap tools.

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