calculate_average

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

No annotations present, so description carries full burden. States it computes and returns mean and detail, implying no side effects. Does not explicitly confirm read-only behavior or mention any constraints.

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?

Three concise sentences with no filler. Immediately states the purpose and key information. Efficiently structured.

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?

Sufficient for a simple compute tool, but missing details on error handling, edge cases, and the discrepancy about the 'mode' parameter. Output schema exists but is not shown; description only vaguely says 'Returns mean and detail'.

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 description mentions a 'mode' parameter that does not exist in the input schema, introducing confusion. Schema already documents 'values' and 'weights' with descriptions. The added information is misleading.

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 computes simple, weighted, geometric, or harmonic mean and gives concrete examples like grade averages, returns, or rates. It distinguishes from sibling tools by referencing related calculators via list_bundles.

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?

Provides explicit use cases (grade averages, returns, rates) and hints at alternatives via list_bundles. Lacks explicit when-not-to-use guidance but sufficient for typical scenarios.

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