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

Beyond the annotations, the description discloses that Vision6 returns no contact data (HTTP 204), that contacts need an email and/or mobile, and that automations may be triggered. These are meaningful behavioral details for a write operation.

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 front-loaded with the write action, then gives the batch limit, required contact fields, return behavior, read-back alternative, and side effect. Every sentence carries useful information.

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 covers the important return behavior and automation side effect, which are especially valuable with no output schema. It is still missing guidance on duplicate handling or partial batch failures, which would matter for this non-idempotent write.

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 only 33%, so the description must compensate. It adds the batch limit and the key email/mobile requirement, but it does not explain the top-level remove_unsubscribers behavior or duplicate/partial-failure handling.

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 states a specific verb and resource: add up to 200 contacts to a list in one request. It also distinguishes this batch operation from the one-by-one alternative and names the sibling used to read results back.

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?

It explains that this is faster than adding one by one and points to vision6_list_contacts for reading contacts back. It does not explicitly say when to choose vision6_create_contact instead, but the batch-vs-single contrast is clear enough for an agent.

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