insert_background_picture

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

No annotations are provided, so the description must disclose behavior, but it only lists mode values. It does not explain side effects like whether the background replaces an existing one, affects all pages, or requires a specific document state.

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 front-loaded sentence with no filler. The mode mapping is included compactly and each element earns its place.

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?

With five parameters and no annotations, this one-sentence description leaves important invocation details unexplained. The output schema may cover return values, but it cannot rescue the missing semantics for 'target' and 'watermark' or the lack of usage context.

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 0%, so the description must compensate, but it only explains 'mode'. The 'target' and 'watermark' parameters remain semantically unclear, and no guidance is given for the required 'doc_id' or 'image_path' beyond their obvious names.

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 specifies the verb and resource: 'Insert a background picture', and adds useful mode semantics. It does not explicitly differentiate from siblings like insert_picture or set_watermark, but 'background picture' strongly implies the intended scope.

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?

There is no guidance on when to use this tool versus alternatives such as insert_picture or set_watermark. The description states what the tool does, but not the conditions, prerequisites, or contexts where it should be preferred.

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