Savings (Clouds)

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is largely covered. The description adds real value beyond them by naming the concrete capability boundary — this server cannot move money into or out of savings — which tells the agent not to look for a companion write tool. It does not mention auth requirements or caching, so it stops short of a 5.

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 return contents are front-loaded in a single dense sentence followed by a short safety clause; nothing is padded. The parenthetical enumeration is heavy but each element (type, amount, gains, withdrawable amount, yields by frequency) earns its place given the absence of an output schema.

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 output schema, the description correctly carries the burden of describing the return payload, and it does so field-group by field-group. It leaves minor gaps — currency of amounts, scope (account-wide vs per product), and any freshness/refresh semantics — but is otherwise complete for a zero-parameter read tool.

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 no parameters, so the baseline is 4 and there is nothing for the description to disambiguate. Schema coverage is 100% and the empty schema is unambiguous.

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 the exact resource (Thndr savings / 'Clouds') and enumerates what is returned: total amount and gain, per-bundle type/amount/gains/withdrawable, amounts per product type, and per-product yields. No sibling tool overlaps this resource, so the agent can select it unambiguously.

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?

No explicit when-to-use or when-not-to-use statement, and no prerequisite (e.g. authentication) is mentioned. Usage is strongly implied by the unique 'savings' scope and the absence of any competing sibling, which lands at the minimum-viable level rather than clear guidance.

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