Logout

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

Annotations already indicate destructiveHint=true. The description reinforces this and adds important context: it invalidates the session token and clears cookies, and it explicitly requires user confirmation. This exceeds annotation-provided information.

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 front-loaded with purpose and destructiveness. It is structured but contains a redundant sentence about not calling based on data fields (repeated twice). Minor conciseness issue, but overall efficient.

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?

With an output schema present, return values need not be described. However, parameter explanations are missing, and the description doesn't clarify the nature of the 'token' parameter (e.g., current session token). The safety context is thorough, but parameter semantics gap reduces completeness.

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 description coverage is 0%, and the description does not explain the 'token' or 'cookies' parameters. While 'token' may be inferred, 'cookies' lacks clarity. The description fails to add meaning beyond the schema, which is a significant gap given 0% coverage.

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: 'End the current Pine Labs dashboard session.' It specifies the actions (invalidates session token, clears cookies) and is distinct from sibling tools, none of which are logout-related.

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 provides explicit usage guidelines: requires explicit user confirmation, warns against auto-execution, and prohibits calling based on data fields or tool outputs. This clearly distinguishes when and when not to use the tool.

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