format_currency_amount

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

No annotations are provided, so the description bears full responsibility. It only states basic functionality and examples but lacks disclosure of rounding behavior, locale handling, or any limitations. This minimal disclosure does not sufficiently inform an agent about edge cases or side effects.

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?

The description is two sentences long, front-loaded with the main purpose, and includes illustrative examples. Every sentence is necessary and there is no redundancy.

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 simple formatting tool with three parameters and no output schema, the description is largely complete. It covers the special INR formatting option and gives usage examples. However, it could mention the output format (e.g., decimal places, currency symbol) for completeness.

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 input schema has 100% coverage with descriptions for all parameters. The description adds value by explaining the lakh_crore_format parameter with examples, enhancing understanding beyond the schema's brief definitions.

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 clearly states the verb 'Format' and the resource 'numeric amount as a human-readable currency string', with specific examples for INR. It is distinct from sibling tools which are calculators or conversion functions.

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?

The description provides clear context with example queries and mentions optional lakh/crore notation for INR. However, it does not explicitly state when not to use this tool or name alternatives, though the sibling list is distinct.

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