Log out of Thndr

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

Annotations declare destructiveHint and idempotent, and the description adds concrete detail: it deletes stored tokens and conditionally signs out of Firebase. Adds value beyond annotations, though it doesn't cover reversibility or post-logout state.

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?

Two short sentences, front-loaded with the primary action and immediately qualifying the parameter behavior. No waste.

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?

Covers the core action, token deletion, and the parameter's effect for a single-param tool. Missing minor details like whether the caller must re-authenticate afterward, but adequate given no output schema.

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 coverage is 0% and forgetIdentity has no description in the schema. The description compensates by explaining exactly what forgetIdentity=true does (also signs out of Firebase), supplying the missing semantics.

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?

States a specific verb (ends session, deletes tokens) on a specific resource (Thndr session). Clearly distinct from sibling login_* tools and read-only getters.

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?

Implies this is the way to terminate a session, and the forgetIdentity clause hints at when extra behavior applies. No explicit when-to-use/when-not guidance relative to auth_status or session-import tools.

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