math_matrix_calculator

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

No annotations are present, so the description carries full burden. It lists operations and size constraints but fails to disclose preconditions (e.g., square matrix for determinant, non-singular for inverse) or side effects. Some behavioral context is provided but incomplete.

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 includes unnecessary clutter like 'Menu ID: matrix_calculator' and a reference to describe_tool. Core information is present but could be more streamlined. It is not optimally conciseness for an agent.

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?

Given the complexity of matrix operations and three undocumented parameters, the description is incomplete. It lacks output format, dimension compatibility rules, and error handling details. The reference to describe_tool acknowledges incompleteness.

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, the description adds little meaning. It lists operations but does not explain that 'b' may be unused for single-argument operations like transpose or determinant. The schema requires 'b' always, but the description does not reconcile this. No parameter details or acceptable values are given.

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 'Matrix arithmetic' and lists specific operations (add, subtract, multiply, transpose, scalar multiply, determinant, inverse) with a size limit of 8x8. This distinguishes it from sibling math tools like math_bitwise_calculator or math_scientific_calculator.

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 does not provide guidance on when to use this tool versus alternatives, nor does it specify prerequisites or limitations beyond size. It mentions using describe_tool for full guidance, shifting the responsibility.

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