log_out

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

Annotations already mark this as destructive and non-idempotent. The description goes beyond those flags by clarifying the specific consequence: the session's cookies are invalidated and must be refreshed in .env. This is actionable context for the agent and does not contradict the annotations.

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 sentences with no filler. The main action is front-loaded, and the critical post-requisite about cookies is stated immediately after. Every word contributes useful information.

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 simple logout tool with an output schema and annotations that already flag destructive behavior, the description covers the core purpose and key side effect. However, it leaves the confirm parameter undocumented and offers no explicit usage guidance, so it is adequate but not complete.

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 has one optional boolean parameter, confirm, with 0% description coverage, and the description never mentions it. The agent receives no explanation of what confirm does or why it might need to be set, making the parameter's semantics unclear despite its self-explanatory name.

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 a specific verb and resource ('Log out of ads.telegram.org') and scopes it to 'this session', making the tool's function immediately apparent. It does not explicitly differentiate itself from sibling tools like revoke_token or check_session, but the session-scoped language is distinctive enough to avoid confusion with most peers.

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 usage context is implied: use this when you want to end the current session. The description adds a useful post-condition ('You will need fresh cookies in .env afterwards'), but it does not explicitly say when to use this tool versus alternatives such as revoke_token or reload_session, nor does it provide any when-not-to-use guidance.

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