create_company

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It only says 'Create a new B2B company' and does not mention any requirements, side effects, idempotency, or constraints (e.g., duplicate name handling). The mutation is implied but lacks detail.

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 a single, concise sentence that is front-loaded with the core purpose. It avoids redundancy and is efficiently structured, though it may be slightly too brief to provide much additional 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 creation tool with 4 parameters, a nested object, and no output schema, the description is minimal. It does not clarify the return value, any required permissions, or how the mainContact nested object is used. The schema covers parameter structure, but the overall context is under-specified.

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 input schema provides 100% coverage for parameter descriptions (name, note, externalId, mainContact). The description adds no parameter-specific meaning beyond what the schema already offers, aligning with the baseline of 3 for high schema coverage.

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 clearly states the action ('Create') and the resource ('B2B company'), distinguishing it from sibling tools like get_company, update_company, and delete_company. The 'B2B' qualifier adds useful context that narrows the scope of the company entity.

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 guidance is provided on when to use this tool versus alternatives such as create_company_location or create_company_contact. The description only states the action, leaving the agent to infer that it is for creating a company entity, without any context on prerequisites or exclusions.

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