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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds real behavioral value: 'A part that could not be read is null, never zero' discloses a failure encoding that would otherwise cause the agent to misread missing data as a zero balance. The sign-in requirement is also restated as an auth trait. It says nothing about result size, pagination, or ordering of the month-by-month series.

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?

Front-loaded with the scope ('Everything you have claimed from the vault, for the wallet you signed in with'), then the content breakdown, then caveats. The middle enumeration is dense but each item maps to a distinct part of the response, and the closing two sentences carry the null semantics and auth note without padding.

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?

There is no output schema, so the description carries the burden of describing return values, and it does: units, entry and current valuation, unclaimed amounts, and monthly totals, plus the null-vs-zero rule. For a zero-parameter, read-only tool with full annotation coverage, nothing an agent needs in order to call or interpret it is missing.

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, so there is nothing for the description to disambiguate and the baseline of 4 applies. The wallet is implicitly supplied by the session rather than a parameter, which the description does clarify via 'the wallet you signed in with'.

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+resource: it returns everything the signed-in wallet has claimed from the vault, broken into real units, historical vs current valuation, pending claims, and monthly running totals. The parenthetical examples (grams of gold, SPY shares, USDY) and the explicit tie to the sign-in wallet make it distinguishable from get_my_vault and get_my_claims without opening any schema.

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?

Usage context is clear: this is the personal, sign-in-scoped timeline view, and it points at get_my_vault for the shared sign-in behavior. It never states exclusions or names a sibling to use instead for a narrower question (e.g. get_my_claims for a flat claim list), so the agent must infer the boundary.

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