create_company

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

No annotations are provided, so the description carries the full burden. It discloses that creating a company is free, and explains the inheritance behavior for optional booleans (None vs. False), including a warning about sending False for paid features. This adds meaningful behavioral context beyond the schema.

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 well-structured: a concise summary, a cost note, then a clear parameter list. Every sentence adds value—no redundancy. The length is appropriate for the complexity (9 parameters, nuanced boolean behavior).

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 the complexity (9 parameters, boolean inheritance, account_id auto-resolve), the description covers key behavioral aspects. It does not mention prerequisites like authentication or output (though output schema exists), but overall it is thorough enough for an AI agent to use 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?

The input schema has 0% description coverage in the schema itself, so the description must compensate. It does so thoroughly: each parameter is explained with examples (time_zone), behavior (boolean inheritance), and account_id auto-resolution. This adds significant value beyond the schema's property types and defaults.

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 'Create a new company (client) under the account.' It specifies the verb (create) and resource (company), and distinguishes from siblings like `create_tracker` by noting that creating a company is free, while creating trackers costs money.

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 explicitly says 'Useful for new-client onboarding' and contrasts with `create_tracker` regarding cost. It also warns about optional booleans defaulting to None instead of False to avoid unintended disabling of features. However, it does not explicitly list when not to use this tool, but the context makes it clear.

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