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

No annotations are supplied, so the description carries the full burden; it does disclose the substantive return content (ownership chain, hash fingerprint), which is genuinely useful behavior-level information. However, it never states that the operation is read-only, whether the chain is scoped to the caller, or what happens when a submission has no recorded sales.

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?

A single tight sentence with no filler, and the returned payload is front-loaded. Nothing could be cut without losing information.

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 and no annotations, the description does well to enumerate return contents, but it leaves the one required input entirely unexplained and says nothing about error or empty-result behavior. Adequate for a simple lookup, but with a clear gap.

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 0% and the single required parameter, submission_id, is never mentioned in the description. The agent is left to guess whether the ID is a submission, an artwork, or a lot identifier, and where to obtain one.

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 names the resource and enumerates its contents specifically: painter attribution, a SHA-256 image fingerprint, and the full ownership chain. That is far more informative than a restatement of the name. It stops short of a verb phrase ('retrieve the provenance certificate') and does not distinguish itself from siblings like get_lot, which also returns artwork data.

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?

There is no statement of when to reach for this tool versus get_lot, list_salon_lots, or my_collection, and no prerequisite or authentication context. The agent must infer from the name alone that this is for verifying an artwork's authenticity and sale history.

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