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

Discloses traits well beyond the annotations: hand-written, asynchronous ("days, not seconds"), nothing generated, brief and name going on a public receipt, the brief possibly printed under the poem, and the reply address never going public. It also names the email origin (lorepunkdoteth@gmail.com). This is exactly the kind of behavioral context annotations cannot carry.

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?

Front-loaded with the core action, then dense but purposeful detail about timing, privacy, and email origin. Every sentence carries information, though it is longer than strictly necessary and could tighten the receipt/privacy clauses.

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 an output schema present, return values needn't be described, and the description covers the async nature, the commission id hand-off, privacy boundaries, and the public receipt. An agent has everything needed to invoke it correctly and set caller expectations.

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 100%, so the baseline is 3, but the description adds real semantics by distinguishing the visibility of each input: brief, from, and for_whom are public-receipt material while reply_to stays private. That goes beyond the per-field schema text.

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 ("Ask Margaret to write a new poem") and makes the nature of the operation unmistakable — a commission, not a lookup. It is clearly differentiated from the read-oriented siblings (get_poem, list_poems, search_poems, random_poem) and routes to commission_status.

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?

Tells the agent what to supply (brief, who's asking, who it's for, how to reach you) and notes that the returned commission id feeds commission_status, which is useful routing. It stops short of explicit when-not-to-use or exclusion guidance, so a 4 rather than a 5.

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