get_auth_help

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

No annotations are provided, so the description carries the burden. It clearly indicates the tool is informational/read-only ('Explain how to obtain...'), which is a useful behavioral signal. However, it does not disclose what the output looks like, whether it performs any side effects, or whether it requires prior authentication.

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 a single, concise sentence that front-loads the action ('Explain') and the subject ('how to obtain Seafile account and library API tokens'). No wasted words.

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 zero-parameter help tool, the description is largely complete: it states the purpose and implies no inputs. The output schema exists, so return values are presumably documented there. It could be slightly stronger by explicitly noting it is a read-only help action, but the current wording is sufficient.

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 tool has zero parameters, so there is no parameter semantics burden. The description correctly implies no inputs are needed, and the schema confirms this. A baseline of 4 is appropriate for a zero-parameter tool.

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 states a clear verb ('Explain') and resource ('how to obtain Seafile account and library API tokens'), which distinguishes it from the sibling auth tools that perform actions like login, rotate, or revoke. It is not a tautology and conveys a help/guidance purpose.

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 implies this is a help tool for obtaining tokens, and the sibling names (auth_login, auth_reauth, etc.) suggest it is the explanatory counterpart. However, it does not explicitly state when to use this tool versus auth_login or auth_status, nor does it mention that it requires no parameters.

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