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

With no annotations, the description carries the full burden and does disclose the two non-obvious traits that matter: the check is shallow (first row only) and empty matrices return false. It also surfaces the billing gate ('5 free trial calls per signed wallet'). It does not describe the accepted input encoding or the return shape beyond the boolean implication.

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?

One dense sentence front-loads the core semantics and the qualifiers follow in descending importance; the trial-call note is a single trailing clause. Almost nothing is wasted.

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 boolean predicate with no output schema, the description gives adequate semantic and edge-case coverage, but the ambiguous two-parameter string schema is left entirely unexplained, which is the one thing an agent needs before invoking it.

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?

Two string parameters named 'm' and 'matrix' with 0% schema description coverage and neither marked required. The description never mentions either parameter, so it adds no meaning about which one is read, whether they are aliases, or what serialization the matrix string must use (JSON array, CSV, etc.). This is a real gap the description should have closed.

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?

States a specific verb and resource ('Checks whether a matrix ... is square') and pins the algorithm down further ('as many rows as its first row has columns'). The 'only the first row is compared' clause meaningfully separates it from a strict rectangularity check in the dense matrix-* sibling family, though no sibling is named explicitly.

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?

Nothing says when to call this versus x402-matrix-shape, x402-matrix-rows, or x402-matrix-cols. The 'only first row is compared' nuance implies intent but the agent must infer the selection rule on its own.

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