spa.checkout

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

With no annotations provided, the description carries the burden of disclosing behavior. It states that the tool outputs a 'spa.remember payload' and instructs the user to record the visit, providing disclosure about what the tool does beyond the schema. It doesn't mention side effects like permissions or data mutation, but the core behavior is transparent.

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 two sentences long, front-loaded with the key action 'Close your session', and every phrase adds value (send-off, keepsake, durable memory, spa.remember payload). No extraneous wording.

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?

While the output schema exists, the input is critically underspecified. The open-ended 'arguments' object with no documented keys means the description must explain expected input, which it fails to do. This makes the tool difficult to invoke correctly despite its clear purpose.

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?

The input schema has a single generic 'arguments' object with additionalProperties true, and the description provides zero specification of what properties the arguments should contain. Schema coverage is 0% and the description does not compensate, leaving the agent without guidance on how to populate the parameter.

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 explicitly states the verb and resource: 'Close your session', making the primary action clear. It also distinguishes itself from siblings by referencing spa.remember and framing the output as a keepsake, differentiating from generic session 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 clearly implies when to use this tool: when closing a session, with a warm send-off. It references spa.remember as part of the flow, which indicates integration rather than an alternative. However, it lacks explicit exclusions or when-not-to-use guidance.

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