stats_stats_describe

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

No annotations provided; the description does not mention behavior on empty arrays, non-numeric inputs, edge cases, or performance. It carries full burden but is 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?

One sentence, very concise, front-loads the key information. Loses a point for being too terse; could add more value without becoming verbose.

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?

With no annotations and 0% schema description coverage, the description lacks details on input validation, handling of edge cases, and expected data types. Output schema exists but does not compensate for missing input guidance.

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%, yet the description only implicitly references 'values' and 'percentiles' without explaining their format, constraints, or default behavior. The 'percentiles' parameter is not described beyond its name.

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 tool computes descriptive statistics (count, mean, median, std, variance, min, max, range, percentiles) from a list of values, distinguishing it from sibling tools like correlation or histogram.

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?

No guidance on when to use this tool versus alternatives or what prerequisites are needed. The description only states what it does, not when to apply it.

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