Log out

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

The annotation readOnlyHint=true directly contradicts the description's promise to delete a session file. Deleting a file is a destructive write operation, not a read-only action. This is a serious inconsistency that misleads the agent about the tool's side effects.

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, front-loaded sentence with no filler. It states exactly what the tool does, which is appropriate for a zero-parameter, low-complexity operation.

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 tool has no parameters and an output schema exists (so return values are covered elsewhere), the description is incomplete because it contradicts the annotation. It also fails to clarify that this is a destructive local action and how it interacts with the server-side session (if at all). The contradiction undermines trust and leaves the agent guessing about actual behavior.

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 zero parameters, and the schema coverage is 100% (empty properties). Since there are no parameters to document, the baseline is 4. The description correctly makes no parameter claims, so no further elaboration is needed.

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 uses a specific verb 'Delete' with a clear resource 'local Benepass session file', which unambiguously states the tool's action. It is distinct from sibling tools like start_login, complete_login, and auth_status, all of which handle session lifecycle but not deletion.

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 usage through the tool name 'logout' and the action 'Delete...session file', but it does not explicitly state when to use this tool versus alternatives (e.g., 'Use when the user wants to end a session' or 'Not for checking status'). The context is reasonably clear but no explicit guidance is provided.

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