lanhu_auth_logout

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

No annotations provided, so description carries full burden. It clearly discloses the destructive behavior (logout and delete managed profile) and the confirmation requirement, which is adequate for a simple authentication action.

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?

Single sentence front-loads the action and requirement, with no extraneous words. Every word earns its place.

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 tool with one parameter and output schema present, the description is sufficient: it explains the primary purpose and parameter requirement. No further behavioral details are needed given the tool's straightforward nature.

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?

Input schema has one boolean parameter confirm with default false and no description. Description compensates by stating '需要 confirm=true 确认', clarifying that the parameter must be true to execute the action, adding meaning beyond the schema.

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?

Description states '登出并删除托管 Profile' (logout and delete managed profile), specifying a clear verb+resource combination. It distinguishes from siblings like lanhu_auth_login and lanhu_auth_status by indicating a destructive action.

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?

Description implies use when logout and profile deletion are needed, and requires confirm=true. However, it lacks explicit context on when not to use or alternatives, though the action is self-evident.

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