deleteMultiImagePostPhoto

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

Annotations already signal destructiveHint: true, but the description adds crucial context: records are irrecoverable, no soft-delete, and advises user confirmation before bulk use. No contradiction with 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?

Six terse sentences, front-loaded with purpose, then usage, required param, alternative, warnings, and return format. 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?

Despite being a simple tool, the description covers purpose, usage guidance, behavioral implications, required parameter, and expected output. Sufficient for an agent to select and invoke correctly.

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 0%, so description carries full burden. It only repeats 'Required: photo_id' from the schema, adding no meaning about what the ID represents or how to obtain it. The name implies the parameter is the photo ID but does not confirm or describe constraints.

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 tool deletes an album photo permanently by ID. It specifies the resource ('portfoliophoto record') and distinguishes it from sibling update tools.

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 provides use conditions: 'permanently removing one photo from an album' and contrasts with hiding via updateMultiImagePostPhoto. Also includes a 'See also' reference to the modification sibling.

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