import_marketing_contacts

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

No annotations provided. Description includes [mutation] hint but no other behavioral details (e.g., whether it overwrites or appends, permissions needed). Minimal transparency.

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 a single line with a mutation tag. It is concise and front-loaded, but could include more key info without being verbose.

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 7 parameters, multiple sources, and many sibling tools, the description is incomplete. It does not cover all sources mentioned in schema, nor explain how it relates to other import tools. No output schema so return values unclear.

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 100%, so each parameter is described. Description adds context that manual and conversations sources are supported, but does not explain csv/txt or clarify relationship between phones_text and phones. Baseline 3 with marginal addition.

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 states it imports contacts to a bulk marketing list and mentions manual and conversations sources, but does not differentiate from sibling tools like import_contacts_csv, import_contacts_manual, etc. The purpose is clear but lacks distinction.

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 sibling import tools. With specific alternatives for each source, the description should indicate scenarios, but it provides none.

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