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

With no annotations, the description fully discloses key behaviors: it runs advisory forensic screens, does not consume verification quota, works anonymously with rate limits, returns an anonymous_user_id for reuse, and requires polling get_verification for results. This goes beyond a simple mutating/read label and sets accurate expectations.

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 dense but every sentence adds value; it front-loads the primary purpose and then layers in transfer/storage, authentication, and alternatives. No fluff or 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?

Given the tool has multiple parameters, an output schema, and sibling alternatives, the description covers the full usage flow: input methods, authentication, result polling, and the recommended alternative. It is self-contained for effective agent use.

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%, but the description directly explains how to use image_base64 and image_object_key, and mentions anonymous_user_id as a return-to-reuse value. It also implies image_filename is optional. This is strong compensation for the missing 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?

The description opens with a specific action, 'Verify a single image's authenticity', and clarifies the exact resource and condition ('when you only have the image and no RAW camera file'). It explicitly contrasts with sibling verify_photo, making the tool's niche unmistakable.

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 gives an explicit when-to-use ('use this when you only have the image and no RAW camera file') and names the alternative for stronger checks ('use verify_photo with a RAW + JPEG pair instead'). It also guides large-file handling via create_verification_upload, showing clear decision logic.

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