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

With no annotations provided, the description carries the full burden of explaining side effects, input expectations, and what happens when the tool runs. It discloses none of that; the only content is a repeated name.

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 definition is extremely short, but this is under-specification rather than effective conciseness. There is no front-loaded useful information, only a restatement of the tool name.

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 calculation tool with three string parameters, no required flags, no annotations, and no output schema, the description is completely inadequate. It omits the formula, parameter semantics, expected output, and any usage conditions.

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 the baseline is 3, but the schema descriptions are minimal templates like 'Cost to process' and 'Markup to process'. The main description adds no meaning, leaving the agent unsure whether markup is an amount or a percentage and why both markup and markupPercent exist.

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 is 'Markup Calc: Markup Calc', which simply restates the tool name and does not state a specific verb or resource. It also gives no distinguishing information versus closely related siblings such as x402-margin-calc, x402-discount-calc, or x402-profit-margin.

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 about when to use this tool or how it differs from alternative calculators. An agent cannot tell whether to choose this over x402-margin-calc or other pricing-related tools.

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