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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about input format, expectations, output, or edge cases. For a computation tool with zero annotation coverage, this is a complete gap.

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 extremely short, but this reflects under-specification rather than efficiency. It contains no useful front-loaded information and cannot be said to 'earn its place' since it repeats the name verbatim.

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?

With no annotations, no output schema, and two ambiguous parameters, the description is entirely inadequate for an agent to call this tool correctly. Nothing an agent needs 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?

Schema description coverage is nominally 100%, but the schema text ('M to process', 'Matrix to process') is tautological and the two string parameters 'm' and 'matrix' are unexplained and confusing for a single-matrix operation. The description adds no meaning to disambiguate them.

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 'Matrix Trace: Matrix Trace' merely restates the tool name/title without adding a verb or clarifying what computing a trace means. It is a tautology that gives an agent nothing beyond what the name already implies.

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 on when to use this tool versus the many matrix siblings (matrix-determinant, matrix-transpose, matrix-multiply, matrix-shape, etc.). No conditions, alternatives, or exclusions are stated.

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