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 burden of behavioral disclosure. The description only states what the tool does mathematically without any information about error handling, input validation, performance characteristics, or what happens with invalid matrices. This is inadequate for a tool with no annotation coverage.

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 concise - a single phrase that directly states the tool's purpose. There's no wasted language or unnecessary elaboration, making it front-loaded and efficient.

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 mathematical operation tool with no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It doesn't address what happens with non-numeric inputs, rectangular vs square matrices, error conditions, or the format of the return value. The context demands more information than provided.

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?

With 0% schema description coverage and a single parameter 'matrix' that has no schema description, the description provides no additional information about parameter semantics. It doesn't explain what format the matrix should be in, what dimensions are supported, or any constraints on the input.

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 '计算矩阵的转置' (calculates the transpose of a matrix) clearly states the verb ('计算' - calculate) and resource ('矩阵的转置' - matrix transpose). It's specific about the mathematical operation, though it doesn't explicitly distinguish from siblings like matrix_add or matrix_multiply, which keeps it from a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when this operation is appropriate, or what distinguishes it from other matrix operations in the sibling list.

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