matrix_transpose

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. It does not state that this is a pure, non-mutating operation, nor does it disclose error behavior for ragged/empty inputs or invalid dimensions, leaving the agent to infer everything.

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?

A single short sentence stating the operation, with the verb front-loaded and no filler or repetition. Nothing could be trimmed without losing 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?

An output schema exists, so return values need not be explained, and the operation is a simple pure function. The only meaningful gap is the absence of error/edge-case behavior (e.g., non-rectangular input), which is minor at this complexity level.

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 0%, but there is only one parameter and its type (array of arrays of numbers) is self-evident from the schema. The description adds no extra semantics such as rectangularity requirements or accepted shapes, but the compensation burden is low for a single obvious parameter.

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 names a specific, unambiguous mathematical operation (transpose) on a specific resource (matrix), which an agent can read without opening the schema. The operation itself is naturally distinct from siblings like matrix_multiply or matrix_inverse, though the description never explicitly contrasts them.

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 related siblings such as matrix_multiply, matrix_determinant, or matrix_inverse, nor any stated prerequisites or exclusions. Usage is only implied by the well-known semantics of 'transpose'.

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