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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only that the result is a numeric amount (useful since there is no output schema), but says nothing about input format tolerance ('Rp 1.000.000', '1jt', '1,5 jt', negatives, decimals) or what happens on unparseable text — the main behavioral risks for a parser.

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 front-loaded sentence with zero filler or repetition. It is efficient, though the terseness leaves the format-tolerance gaps noted above rather than resolving them.

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?

For a one-parameter read-only utility with rich annotations, the definition is minimally viable: the agent knows what goes in conceptually and that a number comes out. It falls short on the parser-specific essentials — accepted input formats and failure behavior — which no other structured field supplies.

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 description coverage is 0% for the single 'text' parameter, so the description carries the full burden. It only labels the domain as 'Indonesian Rupiah text' and provides no accepted-format examples, digit-grouping or separator conventions, or tolerance rules that would tell an agent what to pass.

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?

Names a specific verb ('Parse') with a specific resource ('Indonesian Rupiah text') and states the output ('numeric amount'), which is exactly the inverse of sibling format_rupiah. It does not explicitly name that sibling or terbilang_rupiah, but the direction of the transformation is unambiguous from the verb.

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 explicit when-to-use or when-not-to-use guidance, and no mention of the obvious alternatives format_rupiah (numeric to text) or terbilang_rupiah (numeric to words). An agent must infer the choice from the verb alone, which is workable but not stated.

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