photos_clear

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

With no annotations, the description carries the full burden. It discloses that the tool trashes (deletes) media, verifies count=0, and may require retry. However, it does not detail permanence, authorization needs, or side effects (e.g., whether recently deleted items become permanently removable).

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 a single sentence with all key information front-loaded. No redundant words; every phrase adds value (advanced, trash, verify, optional cleanup, retry condition).

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?

Given no output schema and destructive nature, the description covers the core behavior, verification step, and retry logic. It does not explain return values or error cases beyond retry, but it is sufficiently complete for an agent to understand the primary function.

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 50% (clearDcim described). The description adds meaning by clarifying clearDcim's default true and its role in removing DCIM sources. The udid parameter is not described, but its purpose (device identifier) is standard. Overall, description adds value beyond schema.

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?

Description clearly states the tool trashes all untrashed image/video from Recently Deleted, verifies count=0, and optionally cleans DCIM source. This is a specific verb+resource combination that distinguishes it from sibling tools like photos_ensure or photos_list.

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?

The description implies advanced usage and mentions 'needsRetry if leftover,' but does not explicitly state when to use versus alternatives or when not to use. It lacks exclusion criteria or alternative tool recommendations.

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