bulk_delete_visuals

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: per-row failure isolation ('a missing visual fails its own row only') and result structure ('One result row per target'). This is genuinely informative and goes beyond a simple statement of deletion.

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 with no fluff. The 'BATCH delete_visual:' prefix is mildly redundant with the tool name, but it effectively front-loads the distinction. Every other word contributes useful information.

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?

The description covers the core action and failure behavior, which is essential. However, it omits any explanation of the reportSessionId parameter, the exact return format, or potential irreversible consequences, leaving notable gaps for a destructive batch operation without annotations or output schema.

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 schema already describes items as 'JSON array of {page, visual}', and the description repeats this without adding new detail. The required reportSessionId is completely unexplained in both the schema and description, and the 50% schema coverage gap is not compensated.

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 'delete MANY visuals in one call', which is a specific verb+resource combination. It explicitly distinguishes itself from the singular delete_visual sibling by emphasizing the batch aspect.

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?

The description implies use for deleting multiple visuals at once, which is clear context. However, it does not explicitly name delete_visual as the alternative for single deletions or include when-not-to-use guidance, so it falls short of a 5.

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