cumulus_wallet

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

With no annotations, the description carries the full load: it does disclose the authentication requirement and 'overview' implies a read-only summary. It does not say what the 'full' flag changes behaviorally, nor anything about scoping, caching, or failures beyond the login requirement.

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?

One front-loaded sentence listing the returned content, followed by the login prerequisite. No padding, though the space saved could have been spent on the undocumented 'full' flag.

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?

An output schema exists, so return values need not be described, but the tool's only parameter is left undefined and no routing against the many cumulus_*/stampcard siblings is given. For an aggregator with an undocumented toggle, this leaves an agent guessing.

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 description coverage is 0% and the single parameter 'full' (boolean, default false) is never mentioned in the description. The one thing the schema cannot convey — what 'full' expands or includes — is entirely absent.

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 concrete resource and its contents: a wallet overview returning points plus coupon/voucher/stampcard counts. That is more specific than a restated name. It does not, however, distinguish itself from siblings like cumulus_points, cumulus_coupons, or stampcards, which return overlapping data.

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?

'Requires login' is a prerequisite, not a when-to-use rule. Nothing says whether to call this aggregator first and then drill into cumulus_points / cumulus_coupons / stampcards, or when to prefer this over those single-resource siblings.

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