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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, yet the description still adds real context beyond them: the creator-only authorization requirement, the connection prompt, the account scoping, and the fact that a missing wallet produces a stated response rather than an error. The main undisclosed behavior is the size/ordering of 'latest withdrawals' — how many are returned and whether there is any paging.

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?

It is a single tight paragraph with the audience constraint front-loaded, followed by the returned data and then the safety boundary — good ordering with no filler sentences. The middle sentence is long and colon-heavy, packing five distinct return elements into one run-on, which slightly hurts scanability.

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 carries the burden of describing return values, and it does so concretely, including the withdrawal status vocabulary (Asked, Approved, On hold, Sent, Received, Paid, Failed) and the available-vs-pending balance distinction. It stops short on volume/ordering of the withdrawals list and on currency or amount formatting, which are the remaining gaps 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 zero parameters, so the baseline is 4 and there is no parameter meaning for the description to add. Nothing in the text conflicts with the empty schema.

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 the resource (the connected creator's Piku Wallet) and enumerates exactly what it returns: balance by currency with available/pending split, total withdrawn, latest withdrawals with status, and the minimum withdrawal amount. It also states the read-only boundary ('it cannot withdraw or move money'), so an agent knows precisely what class of operation this is, and no sibling tool in the list overlaps with wallet 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?

It gives an explicit audience and precondition — 'Creators only, on their own Piku account (asks them to connect)' — which tells the agent when the call will succeed and that a connection prompt may occur. It also covers the degenerate case ('When the wallet is not open on the account, says so'). It lacks explicit when-not/alternative routing, but no sibling tool is a plausible substitute, so the omission is minor.

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