auth_oauth2_callback

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no statement about side effects (session/token issuance), state validation, idempotency, or auth requirements. Only the bare POST method hints at mutation.

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?

It is very short and front-loads the method/path, but the 'Tags: Auth Controller' line is generator noise that adds no value. Efficiency comes from omission rather than deliberate editing.

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 an OAuth2 callback with a nested required body, no output schema, and no annotations, the description leaves critical questions unanswered (what it returns, whether it establishes a session, what state is validated). It is not sufficient to call the tool correctly.

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?

Schema coverage is only 50%: the confirm flag is documented in the schema, but code, state, and provider in the nested body object are undocumented. The description adds no parameter meaning whatsoever, so it fails to compensate for the coverage gap on a nested request body.

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 reads 'POST /api/auth/oauth2/callback' plus 'Callback from OAuth2', which essentially restates the tool name rather than explaining what the endpoint does (e.g. exchanges the OAuth2 code for a session/token). It gives the HTTP method and path, but no functional verb that distinguishes it from the sibling auth_oauth2_authorize.

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?

There is no guidance on when to call this versus auth_oauth2_authorize or auth_login, no mention that it is the redirect target of the OAuth2 flow, and no exclusions. An agent must infer usage entirely from the endpoint name.

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