util_median

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

The description offers no behavioral details such as how the median is computed (e.g., sorting required, handling of even-length arrays), edge cases, or return format. With no annotations provided, the description carries the full burden of disclosure but fails to add meaningful context beyond the tool name.

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 a single, clear sentence with no extraneous information. It is appropriately concise and front-loaded, earning its place without waste.

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 utility tool with one parameter and no output schema, the description is adequate but minimal. It does not specify important details like whether the array is sorted internally or the return type (e.g., number), leaving some gaps for the agent.

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 describes the 'values' parameter as '价格数组' (price array), and coverage is 100%. The description adds no additional meaning beyond the schema, so it meets the baseline but does not enhance understanding of the parameter's role or constraints.

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 '计算数组的中位数' (calculate the median of an array) uses a specific verb and resource, clearly indicating what the tool does. It effectively distinguishes itself from sibling tools like util_average, util_quartile, and util_min by specifying the median operation.

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 explicit guidance is provided on when to use this tool over alternatives like util_average or util_quartile. While the purpose is clear, the lack of context for selection among many statistical utilities leaves the agent with only the name to infer usage.

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