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

Annotations carry only a title, so the description bears the full behavioral burden. It discloses one useful fact — each item carries a submission_id — but says nothing about read-only nature, ordering, pagination, or what an empty collection means.

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?

Two short clauses with no filler and the key detail (auction-won ownership, submission_id) front-loaded. The parenthetical phrasing is slightly telegraphic but nothing is wasted.

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 trivial no-param, no-output-schema list tool this is borderline adequate: it tells the agent what the collection contains and one field it will receive. It omits collection size, ordering, and the practical next step, which an agent would need to act on the results.

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?

With zero parameters there are no semantics to explain beyond noting that returned items expose a submission_id, which the description does. Baseline 4 applies for a parameterless tool.

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 paintings you own (won at auction)" names the resource and its scope, which implicitly separates it from my_submissions and browse_gallery. It never states the verb (list/retrieve) or that it returns a collection, leaving the agent to infer that from the name.

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 a hint of the downstream path ("a submission_id you can resell") but no explicit guidance on when to call this instead of my_submissions or browse_gallery, and no naming of resell_artwork as the follow-up tool. Usage is entirely implied.

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