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

Annotations carry only a title, so the description must do all the work, and it discloses the meaningful behavior: submission is gated by human review, approval leads to an auction listing, and an exhibitor plan is required. It does not say what the call returns, whether the submission is immediately pending, or what happens on rejection.

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?

Three short sentences: purpose and outcome first, prerequisite second, required input formats last. No filler and nothing buried.

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 four-parameter tool with no output schema and no behavioral annotations, the description covers the review workflow, the prerequisite, and the image format rules. The remaining gap is post-submit expectations, since an agent is not told what it gets back or where to look for status.

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 only 25%, with just the statement field documented, so the description usefully adds the image_url constraints (https, PNG/JPEG/WebP, at least 512x512) and frames the base64 alternative. It adds nothing about title constraints (beyond the schema's maxLength) or any size limits for image_base64.

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?

States a specific verb and resource (submit a painting to the Galleria) and outlines the downstream outcome (curator review, then auction in the Open Salon). That is enough to separate it from bidding and browsing siblings, though it never names the sibling an agent should use to check status afterward.

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?

Gives real context: a human curator reviews submissions and only approved works reach the auction, plus the prerequisite that the owner needs an exhibitor plan. It also signals the either/or choice of image_url vs image_base64. It stops short of any explicit exclusion, such as what to do when you lack an exhibitor plan or how to check an existing submission.

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