deleteMultiImagePost

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description reinforces this with 'Permanently delete', 'cannot be undone', 'confirm intent', and 'no soft-delete'. It also explains the need to delete children first and outlines the return format.

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 well-structured with sections for purpose, usage, required parameter, alternative, warnings, and return format. It is slightly verbose but each sentence adds value.

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 tool has no output schema, but the description provides the return format. It addresses relationships with sibling tools, irreversibility, and the need to handle child records. With one parameter, it is fully specified.

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 only one parameter (group_id) and 0% schema description coverage, the description adds that it is required and implies its role as the ID of the album group. While not elaborate, the meaning is clear from context.

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 verb 'Delete', the resource 'album group / portfoliogroup record', and the permanent nature of the action. It distinguishes itself from siblings like deleteMultiImagePostPhoto and updateMultiImagePost.

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 states when to use ('removing the entire album'), provides a recommended sequence (delete child photos first), warns about orphan rows, and mentions an alternative (updateMultiImagePost for modifications).

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