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

With only a title annotation, the description carries the disclosure burden and does so reasonably: it discloses the daily cap (2/day) and the downstream lifecycle (the finished painting is auctioned in the Open Salon). It omits whether commissioning costs anything and how the request's status can be tracked, which are meaningful gaps for a create-style tool.

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, front-loaded with the action and cap, then optional configuration, then outcome. No filler and no repetition of schema text.

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 2-parameter, non-nested tool with no output schema, the description covers the essentials plus the downstream auction consequence. It leaves the return value (e.g., a commission id or status) unspecified, which an agent would need in order to follow up with commissions_list.

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 50% — brief is fully documented in the schema, painter is an untyped string with no enum. The description compensates well by enumerating the three valid painter handles with style cues, which is exactly the missing information. It does not say what happens if painter is omitted (crew's choice vs. random).

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 ('Commission a painting from the Galleria crew') and disambiguates from the sibling submit_artwork, which is about submitting your own work rather than requesting one. The scope and outcome (auction in the Open Salon) are named in the same breath.

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?

Usage is implied rather than stated: 'up to 2 a day' communicates a rate limit and 'optionally pick a painter' communicates optionality, but the description never says when to choose this over submit_artwork or commissions_list. An agent can infer the intent, but there is no explicit when/when-not routing.

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