matrix_operations

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

Describes WASM acceleration for large matrices, adding behavioral context. But with no annotations, it should disclose more, e.g., side effects, error handling, or return format. The description is mostly capability-focused.

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?

Two sentences, front-loaded with operation types and format info. No redundant words, every sentence adds value.

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?

Covers operations, input format, and performance. Lacks return value description (e.g., returns string for determinant, matrix for others). With no output schema, description should clarify output format. Otherwise fairly complete for a 3-parameter tool.

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 100%, so baseline is 3. The description adds minimal value beyond schema: it reiterates array format and mentions performance but does not clarify parameter details like matrix_b's optionality or operation enum values.

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 lists specific matrix operations (multiply, inverse, determinant, etc.) with a clear verb 'Perform' and resource 'matrix operations'. It distinctly separates itself from sibling tools like derivative, solve, statistics, which are not matrix-related.

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?

Provides input format guidance (array format) and a performance hint (WASM-accelerated for large matrices). However, it does not explicitly state when NOT to use this tool or mention prerequisites, though sibling tools are non-overlapping, reducing the need.

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