Sorts an array of numbers by distributing values into configurable buckets, sorting each bucket, and concatenating the results into ordered output.
Sort numbers using the bucket sort algorithm. Distributes elements into buckets, sorts each, then concatenates.
| Name | Required | Description | Default |
|---|---|---|---|
| array | Yes | Array of numbers to sort | |
| bucket_count | No | Number of buckets (default: sqrt of array length) |
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It explains the algorithm's internal steps (distribute into buckets, sort each, concatenate), which adds useful context, but omits return format, input mutation, edge cases, and performance characteristics.
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, front-loaded with the purpose and followed by a concise algorithm summary. No wasted words, and the structure is easy to parse.
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 deterministic sorting function with complete parameter schema and no annotations, the description covers the essential what and how. It could explicitly state the return value (sorted array) and edge-case behavior, but the core is sufficient.
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 100%, so both parameters are already documented. The description mentions buckets conceptually but adds no new syntax, defaults, or constraints beyond what the schema provides.
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?
States a specific verb (sort), resource (numbers), and algorithm (bucket sort), distinguishing it from sibling sorting tools like radix_sort or counting_sort by naming the method. An agent can immediately tell what the tool does.
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 bucket sort versus other sorting tools, nor any constraints, prerequisites, or alternatives. Usage is only implied by the algorithm name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.