matrix_info

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

With no annotations, the description is too vague. It doesn't state whether the operation is read-only, has side effects, or requires any prerequisites. The minimal detail leaves behavioral expectations unclear.

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 a single short sentence, which is concise but under-specified. It sacrifices informativeness for brevity, failing to add value beyond the tool name.

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?

Although an output schema exists, its content is not visible. The description fails to define what 'structural and numerical information' entails, leaving significant ambiguity about the tool's output and capabilities.

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%, so the description must compensate, but it adds no meaning about the 'matrix' parameter beyond its data type. The description does not explain format, constraints, or typical usage.

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 clearly states the tool computes structural and numerical information about a matrix, using a specific verb and resource. It distinguishes from siblings like matrix_decompose or matrix_multiply, though not 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?

No guidance on when to use this tool versus alternatives (e.g., matrix_decompose, eigen_decomp). No scenarios for appropriate use or exclusions are provided.

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