create_company

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

With no annotations, the description fully discloses behavior: creation is free, boolean parameters inherit account defaults unless explicitly set, and warns that sending 'False' on paid features would disable them. This prevents accidental misconfiguration.

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?

Well-structured with a header, usage paragraph, and bulletized parameter list. Slightly verbose on redundant notes (e.g., billing statement could be in general context), but every sentence earns its place.

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?

Covers all 9 parameters, required vs optional, default behavior, and usage nuances. No additional information needed for correct invocation; output schema is available, so return values are not required.

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?

Despite 0% schema coverage, the description explains each parameter in detail: acceptable values (e.g., time zone examples), defaults, and the critical None vs False distinction. This fully compensates for the schema's lack of descriptions.

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?

Description opens with 'Create a new company (client) under the account' – a specific verb+resource pairing. It distinguishes from siblings like 'delete_company' and 'update_company' and contrasts billing with 'create_tracker'.

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?

Explicitly states 'Useful for new-client onboarding' and compares with 'create_tracker' for cost context. Provides default reasoning but lacks explicit when-not-to-use guidance.

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