authorize

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

With no annotations provided, the description must disclose behavioral traits. It mentions that the tool 'Opens a browser and waits for the local callback,' which is useful. However, it does not explain what happens on success or failure, or any side effects like setting environment variables or blocking behavior.

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 two concise sentences, front-loading the core action and prerequisites. Every sentence adds value without redundancy.

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?

Given the tool's complexity (OAuth authorization), the description lacks information about return values, errors, or what happens after the callback. Since there is no output schema, the description should cover outcomes but does not.

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 input schema has 100% parameter description coverage. The tool description does not add significant meaning beyond the schema: it mentions the browser opening and waiting, which aligns with the parameters. Since schema covers parameter details, a score of 3 is appropriate.

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: 'Start Cloudreve v4 OAuth (authorization code + PKCE).' It uses a specific verb ('Start') and resource ('OAuth'), and distinguishes it from siblings like 'auth_status' and 'logout'.

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 mentions prerequisites: 'Requires CLOUDREVE_CLIENT_ID and CLOUDREVE_CLIENT_SECRET,' which helps the agent know when it's usable. However, it does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions.

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