Photos: Delete items

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

Goes well beyond the destructiveHint=true annotation: it discloses recycle-bin placement, the case where items are permanently unrecoverable ('otherwise they're gone'), and that a large delete runs asynchronously returning a handle for photo_task. This is exactly the safety/async context annotations cannot convey.

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 core action and scope, then layers destructiveness, async behavior, and the alternative in tight sentences. Every sentence earns its place with no redundancy.

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 destructive two-param mutation with no output schema, it covers safety (recycle bin vs. permanent), async result handling (photo_task handle), confirmation, and the nearest alternative. Nothing an agent needs for correct invocation is missing.

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 both `ids` and `space` are fully documented in the schema. The description adds only 'by id' and 'the files themselves', which the schema already implies; baseline 3 applies when schema does the heavy lifting.

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 ('Delete Synology Photos items (the files themselves) by id') and immediately disambiguates from album removal via 'photo_album remove'. An agent can distinguish it from delete_photo_folders, delete_photo_albums, and delete_files without opening schemas.

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?

Gives an explicit alternative ('To only take items out of an album, use photo_album remove') and a prerequisite ('Confirm with the user first'). It doesn't address all sibling confusions (delete_photo_folders, delete_files) or the space-scoping choice, but the highest-risk alternative is covered.

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