AwardWallet connection status

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive traits, so the bar is lower; the description still adds real value by disclosing what the response reveals (which APIs are usable, credential source, mode flags, entity counts) and its diagnostic role. It stops short of 5 only because it says nothing about auth requirements or caching/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?

A single front-loaded sentence that packs the return contents and the diagnostic use case without filler. It is slightly dense with enumerations but every clause earns its place.

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?

With no parameters and no output schema, the description carries the burden of describing what the agent gets back, and it does so (APIs, credential sources, mode, counts) plus the reason to call it. Only missing element is any hint about field naming or error semantics.

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 takes zero parameters, which sets the baseline at 4; there is no input surface that needs further explanation.

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 names a clear verb (shows) and enumerates concrete resources: available AwardWallet APIs, credential provenance, demo/read-only mode, and people/account counts. It is distinguishable from the sibling list/search tools, though it never explicitly contrasts itself with them.

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?

It gives a clear diagnostic context ('Useful to explain missing data or configuration errors'), telling the agent when this tool is the right call. It does not name alternatives or state when not to use it, so it stops short of the top band.

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