crm_create_company

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Create a new company with validated properties', which implies a write operation but lacks details on permissions needed, whether creation is idempotent, error handling, or response format. The mention of 'validated properties' hints at input validation but doesn't specify rules or outcomes.

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, efficient sentence that front-loads the core action ('Create a new company') without unnecessary words. Every part earns its place by adding value about validation.

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 (2 parameters with nested objects, 0% schema coverage, no output schema, and no annotations), the description is inadequate. It doesn't explain parameter meanings, behavioral traits like error handling, or what 'validated properties' entails, leaving significant gaps for a creation tool in a CRM 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 0%, so the description must compensate for undocumented parameters. It mentions 'validated properties' but doesn't explain what 'properties' or 'associations' parameters mean, their structure, or validation rules. This leaves key semantics unclear beyond the basic action.

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 verb ('Create') and resource ('new company'), making the purpose evident. However, it doesn't distinguish this tool from its sibling 'crm_batch_create_companies', which also creates companies but in batch mode, leaving room for improvement in sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives like 'crm_batch_create_companies' for multiple companies or 'crm_create_contact' for other CRM entities. It mentions 'validated properties' but doesn't explain what validation entails or prerequisites for use.

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