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

With no annotations provided, the description carries the full burden and does so richly: it discloses that unenriched firmographic fields read `collected: false` with a 'not yet collected' note rather than a guess, that moves include a real analysis date, that untracked companies return { covered: false }, and that batch entries are order-preserving and status-tagged. These are non-obvious data-freshness and coverage behaviors an agent could not infer from the schema.

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-loads the trigger conditions before the payload description, which is the right ordering for an agent deciding whether to call. It is dense and runs long in its parenthetical field list, but nearly every clause carries actionable information rather than filler.

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?

No output schema exists, so the description must describe returns — and it does, covering the profile contents, the covered:false case, and batch status tags. For a 3-param, annotation-less read tool, an agent has everything needed to call it correctly and interpret the response.

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 100%, so baseline is 3, and the description edges above it by adding semantics the schema lacks: the mutual exclusivity rule ('Omit domain/name when using this'), result ordering ('in the order given'), and the per-entry `status` value set (account / public / not_covered / ambiguous). The maxItems 10 and domain-preference hints are largely restatements of the schema.

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?

States a specific verb+resource with concrete triggers ('who competes with a company', 'what a competitor recently did', 'competitive overview of one or more domains') and spells out the returned payload (firmographics, recent strategic moves, report links). It stops short of naming how it differs from the sibling find_competitors, whose apparent purpose overlaps with the first trigger phrase.

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?

Gives explicit when-to-use triggers tied to user utterances, plus a clear batch condition ('Pass `companies` instead of domain/name to look up several companies in one call'). It never states when NOT to use it or routes the agent to alternatives like find_competitors, get_market_landscape, or get_comparison, so sibling selection remains partly inferred.

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