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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly states the return behavior (competitors with strategic taglines) and the source of the data. It does not mention limitations like data freshness or potential empty results, but for a simple read-only lookup, the key behavior is transparent.

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 two sentences with no wasted words. The first sentence immediately states the core purpose, and the second adds the return value and use cases. Every part contributes value.

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 one parameter, no annotations, and no output schema, the description provides sufficient context: it names the input, explains the output (competitors with taglines), and suggests use cases. It stops short of detailing the exact response structure, but the simplicity of the tool makes this acceptable.

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 covers 100% of the parameters with a clear description ('Company name, ticker, or slug'). The tool description adds no additional parameter-level detail, so the baseline of 3 is appropriate since the schema does the heavy lifting.

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 ('Find') and resource ('named competitors of a company') with a clear source ('AskCyborg's analyst panel'), distinguishing it from sibling tools like search_companies and compare_companies. It also specifies the output ('one-line strategic tagline').

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 provides explicit use cases ('Useful for competitive landscape analysis, M&A short-listing, or pricing reference checks'), giving clear context for when to use it. However, it does not explicitly state when not to use it or name alternatives, so it lacks the exclusionary guidance required for a 5.

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