Log Out

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

The description adds concrete behavioral consequences beyond annotations: it reveals that logging out reverts to a guest session with '20 free credits/day' and that web app account remains unaffected. This aligns with the destructiveHint and idempotentHint annotations while providing valuable extra context about the state change and side effects, which annotations alone do not convey.

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 just two sentences, front-loaded with the primary action, and every word adds value. It mentions the key outcome (guest session), a constraint (credits), and an exclusion (web app account), all in 20 words. This is exemplary conciseness.

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 parameterless logout tool with no output schema, the description is complete: it states the action, the resulting state, and the boundary of effect. The annotations fill in the destructive and idempotent properties, and the description covers everything else an agent needs to invoke it correctly.

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, so the empty schema fully covers the parameter space. Per the baseline rule, a score of 4 is appropriate since no parameter explanation is needed, and the description adds no redundant parameter details.

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 opens with 'Log out of your GlassyPic account', a specific verb+resource that clearly states the action. It also explains the result of logging out (reverts to guest session) and explicitly distinguishes the tool's scope from a web app account, setting it apart from sibling operations like login or status.

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 clear context for when to use the tool: ending a GlassyPic session. It includes an explicit when-not by stating 'Your web app account is not affected', signaling that this tool is not for logging out of the web app. The mention of guest credits hints at the post-condition, giving enough guidance for an agent to decide.

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