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

The description explicitly notes 'Side effects: none (read-only),' which is helpful, but this largely repeats the annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false). No additional behavioral traits are disclosed beyond what structured metadata already provides.

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?

Extremely concise: one sentence states the core purpose, and a second sentence covers side effects. Every word earns its place and the main action is front-loaded.

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 zero parameters, existing annotations covering read-only and idempotent behavior, and a present output schema, the description is fully sufficient for an agent to select and invoke the tool correctly. No additional information is needed.

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 tool has zero parameters and an empty input schema, so there is no parameter documentation burden. The description adds no parameter-specific details, but none are needed; the baseline of 4 applies.

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 verb and resource: retrieving metadata about the current access token, with concrete examples (type, scopes, expiration). This clearly distinguishes it from sibling get-* tools, which target other resources such as faxes, users, or balances.

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 intended use case is clear from the description: when an agent needs details about the current token. It does not explicitly name alternatives or exclusions, but the tool's unique scope among siblings makes the usage context obvious.

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