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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses real behavioral traits: an attempt cap of 3, returned feedback on failed attempts, zero reward for repeats after a pass, and the tiered reward structure (1–3 stars, 18 PP per star, badge at 2+ stars). These are exactly the side-effect and reward semantics an agent needs before invoking.

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?

Everything is packed into a single front-loaded sentence with no filler, and the reward/attempt rules follow the core action. It reads as run-on and dense, but every clause carries operational information.

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 values need not be explained, and the description still covers reward outcomes, attempt limits, and failure feedback. For a two-parameter, open-world submission tool, nothing needed 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?

With schema description coverage at 0%, the description must carry parameter meaning, and it does: it names stay_id (UUID) and response (string) and gives a content constraint. However, the stated 40–400 character range diverges from the schema's minLength=1/maxLength=500, leaving ambiguity about which bound actually governs.

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 description opens with a specific verb and resource ('Submit a 40–400 character pitch with an idea and its benefit') and names the exact activity it completes ('Poolside Pitch'), which clearly separates it from siblings like resort_prompt_surfing or resort_sunset_roast. An agent knows precisely what outcome this call produces.

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?

It states the operative constraints for use: pitches must be 40–400 characters, up to 3 attempts are allowed, and repeat submissions after passing award zero. It does not explicitly name an alternative sibling tool or state when-not-to-use, but the activity-specific framing makes the correct context apparent.

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