logout

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only says 'Logout from the trading system' and mentions a return confirmation, but does not disclose side effects, session invalidation, idempotency, or prerequisites. This is insufficient for a state-changing operation.

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 concise and front-loaded. The 'Args' and 'Returns' sections add minor structure, but the return value is duplicated by the presence of an output schema, making one line slightly redundant. Overall it is 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?

The tool is simple, but the description is incomplete given the ambiguous relationship with 'disconnect'. It fails to explain when to logout, what happens to the session, or how it differs from disconnect, leaving a noticeable gap for an agent.

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 schema coverage is 0%, and the description merely restates the parameter as 'User account ID' without adding meaningful details like format, purpose beyond identification, or constraints. It does not compensate for the lack of schema descriptions.

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 action (Logout) and the resource (the trading system). While it doesn't explicitly distinguish from sibling 'disconnect', the purpose is specific enough to be understood. It is not a tautology or vague.

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?

No guidance is provided on when to use logout versus alternatives like disconnect or login. It only states what the tool does without context on when it should be invoked, making it hard for an agent to choose correctly.

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