compound_interest

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

With no annotations, the description carries the full burden. It discloses the cost ($0.001 USDC via x402), which is a non-obvious constraint. However, it fails to mention any other behavioral aspects such as whether it is a read-only calculation, what output format is returned, or any limitations. The cost disclosure is a small positive, but transparency is otherwise minimal.

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 extremely short—one sentence—but this is under-specification rather than effective conciseness. The sentence includes irrelevant cost info but omits essential functional details. Every word should be useful, and here the core purpose is missing.

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 financial calculation tool with no output schema and a generic parameter wrapper, the description is severely incomplete. It does not explain how the tool works, what inputs are required, what the result represents, or any example usage. Even with the cost notice, an agent cannot correctly invoke this tool based on the provided information.

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 schema only defines a generic 'params' object with no specific fields. The description does not compensate by listing expected parameters like principal, interest rate, compounding frequency, or time. It adds zero semantic value beyond the schema, leaving the agent without any clue what to provide.

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 'compound interest — Finance & Math tool' merely restates the tool name and broad category. There is no verb or explicit statement of what the tool computes, such as calculating compound interest from principal, rate, and time. It does not differentiate from sibling tools like simple_interest_calc.

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 use this tool versus alternatives. It does not mention scenarios, prerequisites, or contrast with other financial calculators. The only additional info is a pricing notice, which is not a usage guideline.

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