zoho_campaigns_call

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

Discloses that destructive operations require literal confirmation, but fails to define 'literal confirmation' or mention other behaviors like return format, error handling, or auth requirements. With no annotations, more detail is needed.

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 concise (two sentences) but at the expense of completeness. It is well-structured for brevity, but earns a 3 due to being overly terse.

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 tool's complexity (generic executor with undocumented parameters), the description is grossly incomplete. It lacks any output schema, operation list, or usage examples, making it insufficient for an agent.

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 the description adds no parameter semantics beyond a vague mention of 'Zoho parameters'. It does not explain the `operation` parameter values, `params` structure, or `confirmation` format.

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 it executes any cataloged operation with Zoho parameters, distinguishing it from specific sibling tools. However, it does not clarify what 'cataloged' means or how it relates to the raw_request sibling.

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 more specific sibling tools. The only usage hint is about destructive operations requiring confirmation, but no comparison to alternatives.

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