calculate_dollar_cost_average

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

No annotations provided, so the description must fully disclose behavior. It only states the calculation purpose, omitting traits like read-only, side effects, or auth requirements. The agent lacks context on what happens during invocation.

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?

Two sentences: one for purpose, one for related tools. No fluff, efficient, and front-loaded with essential information.

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?

Output schema exists but is absent from the description; the description mentions 'portfolio value and performance' but not specific output metrics. Given 4 required parameters, it's adequate but could clarify what the output contains.

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 100% with clear descriptions for each parameter. The description adds minimal extra meaning beyond 'recurring crypto investments.' Baseline 3 is appropriate as schema does the heavy lifting.

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 it calculates DCA portfolio value and performance for recurring crypto investments. The verb 'Calculate' and specific resource are explicit, and it distinguishes from siblings by referencing 'crypto' and the list_bundles tool.

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 suggests seeing list_bundles for related calculators, implying context but not explicit when-to-use or exclusions. It does not differentiate from alternative crypto tools like calculate_crypto_profit_loss.

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