Sign out

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds the crucial detail of what is actually destroyed: the locally saved session and, by default, the sign-in browser profile. It also implies the server-side session persists unless serverSide=true, which is real behavioral value beyond 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?

A single front-loaded sentence with no filler, with the default behavior parenthetically scoped rather than buried in a second paragraph.

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 two-param destructive tool with annotations covering the safety profile and no output schema, the description gives an agent enough to call it correctly, though it omits any note about re-authentication being required afterward.

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 100%, so both parameters (serverSide, keepBrowserProfile) are already documented. The description only restates the default for the browser profile, adding little beyond the schema; baseline 3 applies.

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 action and target: forget the saved Axcel session on this computer, plus the sign-in browser profile by default. It is clearly separable from the axcel_login_* siblings, which establish rather than remove a session.

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 explicit guidance on when to call this versus alternatives such as axcel_login_diagnose, nor on whether it should precede a re-login or a switch of accounts. Usage is only inferable from the name and the word 'Forget'.

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