POST /companies

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

Annotations already state destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety frame is covered. The description adds nothing beyond that frame: it does not explain that the write is irreversible, that duplicates are possible on retry given non-idempotency, or that SNIPEIT_CONFIRM_WRITES may require the confirm token (only the schema mentions this).

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 first sentence is front-loaded and efficient, but the generator provenance ("Generated from Snipe-IT OpenAPI operation companies-1") is noise that earns no place in an agent-facing definition. The result is short but under-specified rather than truly concise.

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?

This is a destructive mutation with no output schema, a nested body, and a confirmation mechanism. The description does not say what is returned, whether the created company's ID is available for follow-up calls, or how the confirm parameter interacts with this write, leaving the agent without crucial operational context.

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 50%, so the description needed to fill gaps and does not. The nested body object's only required field (name) and the confirm security gate are documented in the schema, but the description says nothing about them, so it adds no semantic value over the structured data.

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 gives a specific verb and resource ("Create a new company"), so the agent knows exactly what is made. It does not distinguish this write from sibling endpoints such as snipeit_gen_companies (list) or snipeit_gen_companiesid (single-company operations), which all sit in the same namespace.

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?

There is no guidance on when to use this versus snipeit_raw_request or the other companies endpoints, and no mention of prerequisites such as the confirmation gate. The agent has to infer usage from the name alone.

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