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

Annotations already establish read-only, idempotent, open-world, non-destructive behavior. The description adds behavioral value by disclosing what the checks cover, including reverse image search links and detection of stolen images, AI-disguised work, and payment scams. It still omits return format and any auth or rate-limit context.

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 purpose is front-loaded in the first two sentences. The third sentence is a long list but remains informative rather than repetitive. The only minor waste is the branded subtitle, which largely duplicates the title.

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?

With no output schema, the description still communicates the kinds of results an agent would expect (reverse image search links and scam/stolen-image/AI checks). Annotations cover the safety profile, and parameters are fully documented, making the definition reasonably complete, though it could be more explicit about the output shape.

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 description coverage is 100%, so both parameters are already documented. The description mentions 'link' and 'picture' in prose, aligning with the url and image fields, but adds no syntax, format, or optionality detail beyond the schema. Baseline 3 is appropriate.

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 states a specific verb and resource: 'Check an art listing,' with clear scope ('before buying') and an enumeration of what gets checked (artist index vs marketplace, reverse image search, stolen images, AI work, payment scams). It distinguishes this tool from other Art Spotter tools implicitly through its listing-verification focus, though it does not explicitly name sibling alternatives.

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?

It gives a clear usage context: use this before buying an artwork. However, it does not include exclusions, prerequisites, or explicit alternatives (e.g., verify_artwork_passport or search_art), so the routing guidance is not fully developed.

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