x402node_math_percentage

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects, authorization needs, or output format. The cryptic note about price ('Price: unknown on Base') adds confusion rather than clarity about behavior.

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 relatively short but includes an extraneous and unclear sentence about price. It front-loads use case keywords but could remove the price line for clarity.

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 tool is simple, but the description lacks details on return value format, error handling (e.g., division by zero), or edge cases. Given no output schema, this is a gap, though the operations are straightforward.

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?

With 100% schema description coverage, the baseline is 3. The description reinforces the meanings of the 'op' parameter (e.g., 'of', 'change') but does not add new information beyond the schema's minimal descriptions.

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 explicitly lists multiple percentage operations and their interpretations (e.g., 'X percent of Y', 'percent change'), making the tool's purpose clear and distinguishing it from siblings like x402node_math_interest.

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 enumerates use cases but provides no guidance on when to prefer this tool over alternatives (e.g., x402node_math_interest) or when not to use it. No exclusions or context for selection.

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