create_auth_oauth_native_token

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

Adds meaningful behavioral context (server-side exchange, no browser session cookie) but doesn't disclose token characteristics, failure modes, or permission requirements. With no annotations, the description carries the burden but reveals only partial transparency.

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?

Two concise sentences pack purposeful detail without redundancy. Front-loaded with the primary action, then clarifies context.

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 4-parameter tool with no output schema and zero schema coverage, the description is insufficient. It explains the flow's rationale but omits parameter semantics, return values, error behavior, and token lifecycle. Need more to enable confident invocation.

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 0%, so the description must compensate. It explains the role of code_verifier (PKCE) and code (authorization code) implicitly, but leaves redirect_uri and nonce undefined. Lacks explicit parameter mapping, leaving agents to infer.

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?

States a specific action ('Exchange a native client's authorization code for a Mealie token') with clear resource and context. Differentiates from the cookie-coupled web callback by explaining the server-side, cookie-free exchange, distinguishing it from sibling auth tools.

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?

Explicitly describes when to use (native client with PKCE, passkey-capable system-browser logins) and contrasts with the web callback that cannot support this scenario, effectively providing when/where-not guidance.

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