Delete a photo's faces

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

Goes well beyond the destructive/idempotent annotations by disclosing that deletion is soft by default, that immediate/compliance make it permanent, and that a nonexistent photo_id still returns deleted=true — a real behavioral trap the agent must guard against. The "Free" cost note is a bonus. Not quite a 5 only because it doesn't cover what data is retained in the soft-delete window.

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?

Front-loads the action, then the default-vs-permanent distinction, then the idempotency caveat, then cost. Three dense sentences with no wasted words.

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?

For a 4-param destructive tool with no output schema, the description covers the action, reversibility, permanence modes, the false-positive return behavior, and cost — everything an agent needs to call it safely and report accurately.

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 100% so the baseline is 3, but the description adds meaning the schema lacks: it explains the default soft behavior and what immediate=true and compliance=true each do (permanent vs audited legal erasure). This genuinely extends the terse schema descriptions.

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?

States a specific verb and resource ("Remove every face indexed from one photo"), scoping it to a single photo and clarifying it removes faces rather than the photo itself. This clearly separates it from siblings like restore_photo and delete_collection.

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?

Explicitly frames the soft-vs-permanent choice, naming restore_photo as the undo path for the default and identifying immediate=true/compliance=true as the permanent route. It doesn't compare against other deletion tools like delete_collection, but the within-tool guidance is clear.

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