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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it discloses nothing: no formula, no domain, no side effects, and no return format. The bare restatement of the name adds no behavioral context whatsoever.

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?

At three words the description is short, but this is under-specification rather than conciseness; no sentence earns its place because the text merely duplicates the tool name. A useful definition would front-load a verb and state what is calculated.

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 tool with no annotations, no parameters, and no output schema, the description is the only information source and it is completely inadequate. An agent cannot determine the domain, the inputs it needs, or what it returns, and the large sibling list of percent/yield tools makes the ambiguity actively confusing.

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 input schema is empty (0 properties) with 100% coverage, so there are no parameters to document or misunderstand. Per the 0-parameter baseline, the description does not need to add parameter detail, though it also fails to clarify whether any implicit inputs are expected.

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 'Percent Yield: Percent Yield' is a pure tautology that merely restates the tool name twice with no verb, resource, or explanation of what the tool computes. It provides no way to distinguish this tool from the many percent/yield siblings such as x402-percent, x402-percentage-change, x402-percent-composition, or x402-yield-to-maturity.

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?

The description offers zero guidance on when to use this tool versus alternatives. There is no context, no exclusion, and no indication of whether this refers to chemistry percent yield (actual/theoretical × 100) or a financial yield calculation, leaving an agent with no basis for selection.

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