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

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

Annotations have readOnlyHint=false and destructiveHint=false. The description discloses that the tool can delete (via delete parameter), auto-link contacts to companies, and that leadScore is computed automatically. This adds behavioral context beyond annotations, though it does not detail rate limits or auth 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?

The description is two sentences plus a contextual note about Rootr CRM. It is front-loaded with key instructions and is reasonably concise, though the CRM context sentence could be shortened without losing essential meaning.

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 15 parameters, 80% schema coverage, and no output schema, the description covers the main behaviors (CRUD operations, auto-linking, leadScore) and provides context about being part of a CRM node. It does not describe return values, but that is expected without an output schema. Overall adequate.

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 coverage is 80% (most parameters have descriptions). The description adds meaning by explaining that omitting contactId creates, including contactId updates, and delete:true deletes. It also clarifies that leadScore is server-side computed and email auto-links to company. This supplements the schema well.

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 can create, update, or delete a contact based on parameters (omit contactId for create, include contactId for update, add delete:true for deletion). It also explains auto-linking and server-side leadScore computation, distinguishing it from sibling list/get tools.

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 explicitly tells when to use each operation (create vs update vs delete) and mentions that email auto-links to company and leadScore is computed server-side (so do not set it). However, it does not compare directly with sibling tools like rootr_crm_upsert_company, but the guidance is sufficient for this tool's internal logic.

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