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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds real context beyond that: it spells out the exact destructive actions (exclude from training data, relabel, dismiss) and reassures that the uploaded pictures themselves are kept, clarifying the true blast radius of the operation. That is meaningful behavioral disclosure on top of the annotations.

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 content is front-loaded by naming findings first, then fixes, which is good ordering. But it is a single dense run-on sentence with a nested parenthetical, making it harder to parse than it needs to be.

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?

No output schema exists, so the description carries the return-value burden, and it does describe the findings returned plus the thumbnail behavior of include_pictures. Combined with the fix semantics, an agent has enough to invoke it correctly, though response shape details are still thin.

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?

With 60% schema coverage, the description compensates well: it maps remove to 'leave pictures out of the training data', relabel to 'relabel them', dismiss to 'dismiss a finding', and explains include_pictures as returning up to 6 thumbnails. Only model_id is left to the schema, which documents it.

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 names the concrete findings it surfaces (near-duplicate pairs, two-label pictures, out-of-category pictures) and the fixes it can apply (remove, relabel, dismiss), which is a specific verb+resource. It does not explicitly contrast itself with close siblings like review_suggestions or correct_labels, so an agent must infer the boundary.

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?

It gives a conditional for the mutating path ('when the user agreed, apply fixes'), which is useful usage guidance. However, it never says when to prefer this tool over review_suggestions, correct_labels, or data_quality, so alternative selection is left implicit.

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