Create, update, or delete a company in a Rootr CRM

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

The description states that deletion is possible by passing `delete: true`, but the annotation `destructiveHint` is false. This is a direct contradiction: the tool can delete companies, yet annotations claim it is not destructive. Per rules, score 1 when description contradicts annotations.

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 two sentences, front-loading the core behavior (operations) and then providing broader CRM context. Every sentence is necessary and no words are wasted.

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?

The description explains the three operations and custom fields, but does not mention that `crmId` is required, that `name` is required for creation (though schema says so), or what the tool returns on success/failure. Given 13 parameters and no output schema, more completeness would be helpful.

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 high (~69-77%), but the description adds value by explaining the role of companyId, delete, and custom fields, and gives example values for size and source. However, it does not cover missing schema descriptions for `address`, `industry`, and `description` parameters, leaving some gaps.

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 three operations (create, update, delete) with specific verb+resource. The title also mirrors this. It distinguishes from sibling tools like rootr_crm_upsert_contact by specifying 'company' as the target entity.

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 explicit conditions for each operation (omit companyId for create, pass companyId+fields for update, pass companyId+delete:true for delete). It references rootr_crm_get for custom fields. However, it does not mention when to use alternatives like rootr_crm_get for reading or rootr_crm_list_companies for listing, though the name 'upsert' implies mutation.

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