matrix_multiply

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

With no annotations provided, the description carries the full burden. It only discloses the return type ('as nested lists') but says nothing about error handling, dimension mismatch behavior, or side effects. This is minimal behavioral disclosure for an operation that can fail on incompatible inputs.

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, concise sentence that efficiently communicates the action, the object, and the output format. There is no redundancy or unnecessary detail.

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 simple mathematical operation with two well-defined parameters and an output schema, the description is adequate for basic use. However, it lacks any mention of dimension compatibility or error behavior, which could be relevant for a matrix multiplication tool, making it slightly under-specified.

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?

The input schema already describes both parameters as 'Left matrix (rows of numbers)' and 'Right matrix (rows of numbers)', providing 100% coverage. The description adds no additional semantic value beyond the schema, so it neither clarifies nor enriches the parameter understanding.

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 uses the specific verb 'Multiply' and clearly identifies the resource as 'two matrices', explicitly stating the operation and the result format as nested lists. This distinguishes it from the broader sibling tool 'matrix_operation'.

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 gives no guidance on when to use this tool versus alternatives like 'matrix_operation', nor does it mention prerequisites such as matrix dimension compatibility. It simply states what the tool does without any contextual usage directions.

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