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

Annotations only declare the generic profile (not read-only, open-world, not idempotent, non-destructive). The description adds real behavioral rules the annotations cannot convey: the 3-attempt cap, zero credit for repeated passes, failure feedback, and the star/PP/badge award math.

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?

Single front-loaded sentence that leads with the task before stacking constraints, parameters, attempts, and rewards. Dense but nearly every clause carries call-relevant information; it is long rather than wasteful.

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?

An output schema exists, so return shape need not be explained. For a two-parameter scored submission tool, the description covers the content constraint, both inputs, attempt limits, and reward outcomes — nothing an agent needs to call it correctly is missing.

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%, so the description carries the full burden — and it does name both parameters with meaning (stay_id as UUID, response as the joke string). However, its stated 15–240 character window conflicts with the schema's minLength 1 / maxLength 500, which could mislead an agent validating input.

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 (write) plus the exact artifact (a 15–240 character resort-themed joke) and names the target activity, Sunset Roast. An agent can immediately distinguish this from resort_poolside_pitch or resort_prompt_surfing without opening the schema.

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 clear operating context: requires stay_id and response, allows up to 3 attempts, failed attempts return feedback, and repeat passes score zero. It never explicitly names a sibling alternative or states when NOT to use this tool, so it stops short of a 5.

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