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

No annotations are provided, so the description carries the full disclosure burden — and it discloses nothing: no computation semantics, no return value, no side-effect or safety profile, no data requirements. 'Covariance: Covariance' contains zero behavioral content.

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?

Two words is technically short, but neither word earns its place — both merely repeat the tool name. This is under-specification, not conciseness, mirroring the 'Process' calibration case where an extremely short but content-free description scores a2.

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 statistical tool with no output schema, no annotations, and an empty input schema, the description is drastically incomplete. An agent cannot predict the output shape, cannot identify the input source, and cannot distinguish this tool from x402-covariance-sample or x402-covariance-matrix. Nothing needed for correct selection or invocation is present.

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 params, 100% coverage trivially), so there is no parameter syntax to document and the rubric baseline is4. However, a covariance computation inherently requires input data, and the description never explains where that data comes from (context, prior tool output, etc.), leaving the agent unable to prepare for invocation. The description therefore adds no meaning about inputs and fails to compensate for the schema's silence on data sourcing.

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 'Covariance: Covariance' — a label-value restatement of the tool name with no verb, resource, or explanation of function. It does not say whether the tool computes, explains, or validates covariance, and it is indistinguishable from siblings like x402-covariance-sample and x402-covariance-matrix based on this text. This is a textbook tautology.

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 text addresses when to use this tool. The sibling list contains near-identical statistical tools (x402-covariance-sample, x402-covariance-matrix, x402-correlation, x402-variance), yet the description provides zero criteria for choosing among them and no exclusions or routing guidance.

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