Exchange Baidu auth code

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

With no annotations, the description must convey behavior. It only states the exchange but omits crucial behavioral details: the code is single-use, possible failure modes, whether tokens are returned in the response, and whether any upstream API calls are made. This leaves the agent uncertain about side effects.

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, direct sentence with no filler. It states the action and the outcome efficiently.

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?

The description is minimal and lacks critical context: it doesn't explicitly state the response structure, error conditions, or that the authorization code becomes invalid after use. There is no output schema or annotations to fill this gap, so the agent may not know how to handle the result.

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 provides no description for the 'code' parameter, and the description merely references 'authorization code' without explicitly mapping it to the parameter. However, the parameter name and the tool's action make the semantics clear enough. The description adds some context but doesn't elaborate on code format, length, or origin.

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 uses the specific verb 'exchange' with the resource 'Baidu OAuth authorization code' and explicitly names the outputs (access and refresh tokens). This clearly distinguishes it from sibling tools like baidu_auth_url and baidu_auth_refresh.

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 usage by naming the input (authorization code) but doesn't explicitly state when in the OAuth flow this should be called or mention alternatives like baidu_auth_refresh. The context is clear enough to infer, but there's no explicit guidance.

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