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

With no annotations, the description carries the full disclosure burden and it delivers almost nothing beyond the verb. It does not say whether stopping is idempotent, what happens to in-flight runs or funds already in motion, whether auth/KYC is required, or whether the operation is reversible — material facts for a control-plane mutation tool.

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 short, front-loaded sentence with no filler or repetition. Its brevity is appropriate to the surface form, though it leaves the definition underspecified rather than compact.

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?

A destructive-flavored control action with no annotations, no output schema, and a fully undocumented parameter needs substantially more than a single sentence. An agent cannot tell from this description what state it will leave the controller in or how to interpret success.

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 coverage is 0% for the single wallet parameter, so the description had to compensate. "For a wallet" signals the parameter's target, but it does not explain why the parameter is optional and nullable (0 required) or what wallet is used when it is omitted — the most consequential ambiguity in the call.

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 ("Stop") and a specific resource ("the HF31 autonomous money controller") scoped to a wallet, which distinguishes it from read-oriented siblings like auto_money_status and auto_money_dedupe_status. It never names a sibling explicitly, so differentiation rests on the verb alone.

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?

There is no guidance on when to invoke this versus alternatives such as auto_money_status (check state first?) or money_run_continue, and no stated prerequisites. The intent to halt a running controller is only implied by the verb, which matches the calibration case for 'no when-to-use, no prerequisites'.

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