midpoint_calc

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

With no annotations, the description carries the full burden. It discloses a monetary cost ('Costs $0.001 USDC via x402') but says nothing about whether it reads, writes, mutates, or how it behaves. This minimal cost information is useful but far from sufficient.

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 technically a single short line, but it earns its place only by providing the cost. It is under-specified, not appropriately concise: it omits the essential purpose and parameters.

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?

This is a utility tool with no output schema, no annotations, and a generic parameter placeholder. The description fails to explain even the basic function, making it impossible for an agent to use correctly.

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 only exposes a generic 'params' object with no specific fields, and the description adds no parameter meaning. The actual inputs for a midpoint calculation (e.g., coordinates) are completely undocumented, so the agent cannot determine how to call this tool.

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 only restates the tool name and category ('midpoint calc — Other Utilities tool') without stating what the tool does. No verb or resource is specified, and it doesn't distinguish this utility from the many other calculation tools in the sibling list.

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?

There is no guidance on when to use this tool instead of alternatives. It merely indicates it's an 'Other Utilities' tool and mentions the cost, but gives no context for appropriate use.

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