zoho_campaigns_move_to_do_not_mail

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

The description adds that confirmation is required, which is important but already evident from the schema's required field and const. No disclosure of side effects, reversibility, or permissions needed. Given no annotations, more detail would be beneficial.

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?

Extremely concise, single sentence. Front-loaded with action and requirement. No extraneous content.

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?

For a simple two-parameter tool, the description covers the core action and a key requirement, but lacks contextual details like prerequisites, results, or error conditions. Acceptable but not fully comprehensive.

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 0%, and description adds no individual parameter explanations beyond noting confirmation. The email and confirmation parameters are only defined by their types and constraints in schema.

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 moves a contact to Do-Not-Mail and explicitly notes a confirmation requirement. This distinguishes it from sibling tools like 'unsubscribe_contact'.

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 alternatives such as 'unsubscribe_contact'. No exclusion criteria or contextual hints provided.

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