run_owler_companies_competitors

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

With no annotations, the description must carry the full behavioral load. It usefully discloses the output fields and the billing model ('1 point per returned record'), but it omits pagination behavior, authentication needs, rate limits, and any safety profile.

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 one front-loaded sentence that identifies the resource, the input, the returned fields, and the cost model. Every clause earns its place with no redundancy or 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?

Given no output schema, the description helpfully lists the fields returned and notes the point cost. It does not explain pagination interplay between max_items and start_page, but the schema covers those parameters fully, so the definition is nearly complete for an agent 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 coverage is 100%, so all parameter semantics are already documented in the schema. The description repeats the company input format (slug or URL) but adds no new meaning for max_items or start_page; baseline 3 is appropriate.

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 names a specific resource (competitors of one Owler company) and the input type (slug or URL), making the tool's purpose unmistakable. It enumerates the returned fields, which further clarifies what the tool does and distinguishes it from general company lookup siblings like run_owler_companies.

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 only states what the tool returns; it gives no explicit when-to-use guidance, no preconditions, and no mention of alternative tools. Without any routing information, an agent must infer usage solely from the name and resource.

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