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

No annotations are provided, so the description carries the full burden — and it discloses nothing: not whether it's a pure computation, a state mutation, or a game move; not its return shape; not any side effects or constraints.

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 long, so not bloated, but this is under-specification rather than conciseness. It fails to front-load any actionable meaning.

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 3-parameter tool with no annotations and no output schema, the description is completely inadequate. An agent has no basis to decide whether to call it, what inputs to supply, or what to expect back.

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 coverage is 100% and the three string params are each documented only as '<name> to process', which is itself uninformative. The description adds nothing beyond the schema, and the schema's own parameter descriptions are near-tautological (n/cols/rows 'to process').

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 literally 'Matrix Zero: Matrix Zero' – a tautology that restates the tool name. It gives no verb, no resource, and no indication of what the tool computes or returns. An agent cannot distinguish it from the hundreds of x402-* math utilities.

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 whatsoever on when to use this tool, what problem it solves, or which siblings (e.g., x402-matrix-*, x402-2048-move) are alternatives. Nothing routes the agent.

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