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

With no annotations, the description carries the full disclosure burden, but it reveals nothing about behavior — how the trapezoid is specified, what the output looks like, or how edge cases are handled. Critically, the input schema is empty even though trapezoid area mathematically requires bases and height, and the description does not explain how inputs are supplied at all.

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 short, but it is under-specification rather than effective conciseness — the two halves of 'Trapezoid Area: Area of trapezoid.' are redundant with each other and with the tool name. The single sentence does not earn its place because it conveys zero information beyond the identifier.

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?

The description is inadequate even for a simple calculator: it provides no input specification, no return-value description, no output schema, and no differentiation from hundreds of nearby siblings. An agent cannot determine how to invoke this tool correctly or when to prefer it over x402-trapezoidal-rule or x402-area.

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 has zero parameters, so under the rubric the baseline is 4 since there are no parameter meanings the description must clarify. The description adds nothing about inputs, but there is nothing for it to document; the larger anomaly of an empty schema for a computational tool is a completeness issue more than a parameter-semantics one.

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 'Trapezoid Area: Area of trapezoid.' is a direct restatement of the tool name x402-trapezoid-area — the title fragment and body say the same thing and add nothing beyond the name. It does not distinguish the tool from semantically close siblings such as x402-trapezoidal-rule, x402-area, or x402-trapezoid-perimeter, so it fails to disambiguate.

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 is given about when to use this tool versus any of the numerous geometry siblings. There is no mention of context, exclusions, or alternatives — the description contains only the tautological phrase and offers an agent no decision-relevant information.

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