add_merge_field

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

No annotations provided; description omits side effects, permissions, or whether adding a field modifies the document persistently. Only states basic replacement behavior.

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?

Two sentences plus Args/Returns section; the Args section mostly repeats schema, and Returns is generic. Could be more streamlined.

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?

Simple tool with one parameter; description covers basic operation but lacks connection to sibling 'execute_mail_merge' and doesn't detail return structure beyond 'success or error'.

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%, but description adds examples ('FirstName', 'Address') for the single parameter 'field_name', clarifying it as a string name. Adequate but minimal.

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?

Clearly states the verb 'add' and resource 'mail merge field', and explains the purpose for mail merge data replacement. Distinct from sibling 'execute_mail_merge' which performs the actual merge.

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?

Implies usage before executing mail merge, but does not explicitly state when to use or not use this tool, nor mention ordering relative to 'execute_mail_merge'.

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