import_contacts_from_crm

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

No annotations exist; the description only labels it as [mutation]. It does not disclose side effects, authorization needs, rate limits, or what happens to existing data. This is insufficient for a mutation tool.

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 sentence with a clarifying dash and mutation tag. It is concise and efficient, though could be slightly more structured with separate usage hints.

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 simplicity of the tool (1 parameter, no output schema), the description provides basic context. However, it omits details like required permissions, success/failure responses, and how it differs from similar import tools.

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?

Input schema has 100% description coverage for the single parameter 'list_id'. The description adds context that the list is for 'marketing masivo' (mass marketing), enhancing schema semantics.

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?

Description clearly states it imports contacts from WAzion's internal CRM to a mass marketing list. However, a sibling tool 'import_crm_contacts' exists without differentiation, slightly reducing clarity.

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 the many other import contacts tools (e.g., import_contacts_csv, import_crm_contacts). The description lacks explicit usage context.

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