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

The description discloses the operation type ('Exchange password grant credentials') which aligns with readOnlyHint=false, but does not add rich behavioral context beyond that, such as token expiration, refresh semantics, or side effects. Annotations already signal non-idempotency and non-destructiveness, so the description adds modest value.

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-loaded with the action and endpoint, and the second sentence adds necessary credential-source context. 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?

Given the tool's moderate complexity (5 params, output schema present), the description is fairly complete: it states the action, endpoint, and where required credentials come from. The output schema covers return values, so lack of description there is fine. Minor gap: it doesn't explicitly frame the overall auth flow or token usage, but that is inferred.

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 100% with all parameters described. The tool description mostly repeats the source of client_id/client_secret already in the schema, and does not add meaning for scope, username, or password beyond their existing schema descriptions. Baseline 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 uses the specific verb 'Exchange' and identifies the resource as 'password grant credentials via POST /oauth/token', clearly distinguishing it from login-account and other sibling tools. It also explains the source of client_id/client_secret, which ties it to the login flow.

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 that a prior login must have occurred ('client_id and client_secret come from POST /v1/login') but does not explicitly state when to use this tool vs alternatives or provide any exclusions. It gives context but lacks explicit usage guidance.

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