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

With no annotations supplied, the description carries the full burden, and it does disclose the shape of the returned policy (mode plus its three allowed values, strict destinations, guardian link) even though no output schema exists. It omits whether this is purely read-only, whether guardian linking can restrict withdrawals, and how mode values affect behavior, so significant behavioral context is missing.

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 compact sentence with no filler, and the key concept ("Money-out policy") is front-loaded. It is arguably over-compressed into a noun-phrase fragment, which costs a little readability but nothing is wasted.

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, no annotations, no output schema and low complexity, the description needs to define what comes back and why an agent would call it. It partially does by naming the three policy components and the mode enum, but leaves the returned structure and the practical implication of each mode unexplained.

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 nothing for the description to clarify. The enum values listed (disabled|autonomous|human_passkey) are return-value semantics, not parameter semantics, so they do not raise or lower this dimension.

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 is a telegraphic field list ("Money-out policy: mode (disabled|autonomous|human_passkey), strict destinations, guardian link") rather than a verb+resource statement. Combined with the name get_withdrawals_config, an agent can infer it returns withdrawal-policy settings, but the description itself never states that it reads/returns configuration and does nothing to distinguish it from siblings like list_pending_withdrawals or prepare_withdrawal.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as prepare_withdrawal or list_pending_withdrawals. The agent must infer from the name alone that this is the pre-flight check before preparing a withdrawal.

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