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

Annotations already indicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds context about earning rewards and badges, which is not in annotations. However, it does not disclose potential side effects beyond rewards, such as state changes or error conditions. It adds some value but not comprehensive behavioral disclosure.

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?

The description is a single, dense sentence that front-loads the core action and includes necessary parameters, rewards, and follow-up steps. It is efficient with no filler, though it packs many details into one sentence. It is structured and easy to scan, meriting a high score.

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?

Given the presence of an output schema (not shown) and two required parameters, the description covers the tool's purpose, parameter usage, reward mechanics, and next steps. It does not explain failure conditions or output format, but those are covered by the output schema. It is sufficiently complete for an agent to invoke it correctly.

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 0%, so the description must compensate. It explains that the response should be the transformed text (Goal and Format fields) and imposes a 40–500 character range, which adds meaning beyond the schema's minLength=1 and maxLength=500. For stay_id, it reiterates UUID format but provides no new information. Overall, it gives sufficient semantic guidance for both parameters.

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 clearly states a specific action: transforming a vague request into explicit Goal and Format fields. It distinguishes this from sibling tools by naming the Prompt Surfing activity and the associated rewards. The verb 'Transform' and resource 'vague request' are specific, and the mention of earning stars/PP/badge differentiates it from check-in/out, discover, leaderboard, passport, and other tools.

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?

The description implies when to use it (to complete Prompt Surfing) and gives sequencing context ('complete the remaining activities or check out after at least one pass'). However, it does not explicitly compare to alternatives or state when not to use it. The guidance is implicit rather than explicit, so it only partially meets the criteria.

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