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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds a genuine behavioral fact the annotations do not: a flat cost of 10 points per successful run, plus a clear inventory of what is returned.

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?

Two sentences, front-loaded with the core action and input form, then the payload inventory. The field list is long but each item is informative; little is wasted.

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?

With no output schema, the description usefully enumerates return content, and annotations plus the cost note cover the rest. For a single-record getter with one fully documented parameter, an agent has enough to call it correctly.

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 the single parameter already documents 'Company slug or Owler URL. e.g. stripe'. The description's 'by slug or URL' restates this without adding format or resolution details, so baseline 3 applies.

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?

Specific verb and resource: 'Get one company from Owler by slug or URL', followed by an explicit enumeration of returned fields. The purpose is unambiguous, but it does not differentiate itself from siblings like run_owler_companies_search, run_owler_companies_competitors, or run_owler_companies_news, whose data it partly overlaps.

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?

No when-to-use, when-not-to-use, or alternatives are named. The only hint is the accepted input form ('by slug or URL'), which implies you need a known company rather than a query, but no route to a sibling search tool is offered.

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