import_crm_contacts

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

No annotations are provided, and the description only adds '[mutation]', which does not disclose behavioral traits like idempotency, overwrite behavior, error handling, or required permissions. This leaves the agent uninformed about important side effects.

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 very short (one line) and lacks structure. While concise, it could benefit from a more structured format explaining behavior and parameters.

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?

No output schema and minimal description. For a mutation tool that imports data, the description should include return value, error handling, prerequisites, and file size limits. This is completely inadequate.

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 input schema covers all 3 parameters with descriptions, achieving 100% schema coverage. The description adds no additional meaning beyond the schema, such as file format expectations or the effect of defaults.

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 verb 'importar' and the resource 'contactos al CRM interno desde un archivo CSV', which is specific and distinguishes it from other import tools (e.g., import_contacts_csv, import_contacts_from_crm).

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 explicit guidance on when to use this tool versus alternatives (e.g., import_contacts_csv, import_contacts_from_crm). The label '[mutation]' implies side effects, but there are no statements about prerequisites, file size limits, or error handling.

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