set_ai_auth

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

No annotations are provided, so the description carries the full burden. It explains that setting credentials enables subsequent ask_ai calls to use login and removes limits, but does not disclose behavior for invalid cookies, error handling, or whether previous credentials are overwritten.

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 well-structured with clear sections (usage scenario, how to get cookie, example). It is concise and front-loads the purpose, with no wasted sentences.

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 one-parameter tool with no output schema, the description covers purpose, usage, and effect adequately. It could mention the return value or success indication, but overall it is complete enough for effective use.

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 already describes the cookie parameter and has 100% coverage, but the description adds significant value by explaining how to extract the cookie from browser developer tools, which goes beyond the schema's definition.

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 the tool's purpose: setting AI Q&A login credentials to bypass anonymous usage limits. It uses a specific verb (设置) and resource (登录凭证), and distinguishes itself from sibling tools like ask_ai which require authentication.

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 explicitly states when to use this tool (when ask_ai prompts limit or needs login) and provides a step-by-step guide on how to obtain the cookie. However, it does not mention when not to use it or alternative approaches.

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