Add a CRM company

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

Annotations provide no safety profile; description adds that slug is derived and de-duplicated, and returns the new record. However, it doesn't disclose whether the operation is idempotent, potential side effects, or authentication needs.

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?

Description is concise at three short sentences, front-loading the main action. No filler, but could be more structured to improve scannability.

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?

With no output schema and no annotations, the description lacks completeness. It doesn't explain optional parameters, expected response format beyond 'returns the new company record', or error conditions. Insufficient for a tool with 4 parameters and no schema descriptions.

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 description must compensate. It only explains 'project' (implicitly) and 'name' (slug derivation), but omits 'notes' and 'domain' entirely. Two of four parameters remain undocumented.

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 tool creates a company in the project's CRM, with slug derivation and deduplication. It distinguishes from sibling add_* tools by targeting companies, but doesn't explicitly differentiate from add_contact or add_lead.

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 on when to use this tool versus alternatives like add_contact or add_lead. The description only implies usage for creating companies, but does not specify prerequisites or when-not-to-use scenarios.

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