byebye

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: locking the session, cleaning up secrets from disk, and displaying a goodbye message. However, it doesn't mention potential side effects like irreversible session termination or whether user confirmation is required.

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 perfectly concise and well-structured in two sentences. The first sentence explains what the tool does, and the second provides usage guidance. Every word earns its place with no redundancy or unnecessary 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?

For a zero-parameter tool with no annotations and no output schema, the description provides sufficient context about what the tool does and when to use it. However, it doesn't specify what happens after execution (e.g., whether the session can be restored or if this triggers a complete shutdown), leaving some behavioral questions unanswered.

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 tool has 0 parameters with 100% schema description coverage. The description appropriately doesn't discuss parameters since none exist, maintaining focus on the tool's action. A baseline of 4 is applied for zero-parameter tools when the description adequately explains the tool's function.

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 the tool's purpose with specific verbs ('End', 'Locks', 'cleans up', 'says goodbye') and identifies the resource ('work session'). It distinguishes itself from sibling tools like 'sleep-session' or 'wake-session' by indicating a permanent termination rather than temporary suspension.

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 explicitly states when to use this tool: 'Use this when you finish working for the day.' This provides clear context for usage and implicitly distinguishes it from alternatives like 'sleep-session' (for temporary breaks) or 'session-status' (for checking state).

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