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. 'Create' implies a write operation, but there's no information about required permissions, whether validation is strict or permissive, what happens on duplicate companies, or what the response contains. The mention of 'validated properties' hints at some validation but doesn't specify what validation occurs or error behavior.

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 extremely concise at just 6 words, front-loading the essential purpose without any wasted words. Every word earns its place, though this conciseness comes at the cost of completeness for such a complex tool.

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 complex creation tool with 2 parameters (one being a deeply nested object), 0% schema description coverage, no annotations, and no output schema, the description is severely inadequate. It doesn't explain the parameter structure, expected return values, error conditions, or behavioral constraints that would help an agent use this tool 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 schema has 0% description coverage for its 2 parameters (properties and associations), and the description provides no parameter information beyond 'validated properties.' The complex nested structure with 16+ property fields and association objects remains completely undocumented in the description, leaving the agent with no semantic understanding of what data to provide.

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 resource ('new company'), making the purpose immediately understandable. It distinguishes from other CRM tools by focusing specifically on company creation rather than contacts, leads, or other objects. However, it doesn't explicitly differentiate from batch creation alternatives like 'crm_batch_create_companies'.

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. There are multiple sibling tools for company operations (crm_batch_create_companies, crm_update_company, crm_search_companies), but the description offers no context about single vs batch creation, prerequisites, or appropriate use cases.

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