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

No annotations are provided, so the description carries the full burden of behavioral disclosure, but it says nothing. There is no indication of whether the tool reads, computes, mutates, or returns data, leaving the agent completely in the dark.

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?

This is under-specification, not conciseness. The description uses its tiny space to restate the name redundantly, providing zero informational value. It is not front-loaded with anything useful because there is no content at all.

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 tool with no annotations, no output schema, and a vast set of sibling matrix tools, this description is completely inadequate. It lacks purpose, usage, behavior, and expected return information, so an agent cannot meaningfully decide to invoke 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?

The input schema is empty (0 parameters, 100% schema coverage), so the baseline of 4 applies — there are no parameter semantics for the description to add. The description does not contradict the schema, and nothing further is needed for this dimension.

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 Rows: Matrix Rows' is a pure tautology — it repeats the tool name without a verb, resource, or any functional explanation. An agent cannot determine whether this extracts rows, creates rows, counts rows, or something else, and the sibling matrix tools (matrix-cols, matrix-transpose) are not differentiated at all.

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 is given about when to invoke this tool versus the many matrix-related siblings. There is no mention of input requirements, output format, or conditions that would make this tool preferable to matrix-cols or matrix-flatten.

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