remove_watermark

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

With no annotations, the description reveals that it removes VML watermarks from all headers, which adds some behavioral context. However, it omits details like whether it affects only specific sections or what happens if no watermark exists.

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 a single, concise sentence of 10 words that immediately conveys the core function without unnecessary detail.

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 simplicity (one parameter, no nested objects) and presence of an output schema, the description captures the main purpose but lacks parameter details and behavioral nuance. It is minimally adequate.

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?

The single parameter 'document_handle' has no schema description (0% coverage), and the tool description does not explain its meaning or format. The parameter's role is only implied by the tool's context.

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 action 'Remove' and the specific resource 'VML watermarks (e.g., DRAFT) from all document headers,' which is distinct from sibling tools like insert_watermark or delete_header.

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 is provided on when to use this tool versus alternatives, nor any conditions or limitations. The description says nothing about when not to use it or related tools.

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