multiply

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

For a pure arithmetic operation, 'Multiply a and b' transparently conveys behavior: no side effects, no mutation, no hidden state. With no annotations provided, the description is adequate, though it does not discuss edge cases like overflow or type coercion.

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 sentence with zero filler, and the core operation is front-loaded. This is appropriately sized for a two-parameter pure function.

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?

The tool is simple, the input schema fully specifies both required numeric parameters, and an output schema is present. Nothing essential is missing for an agent to call this tool correctly.

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 clarify parameter roles. It identifies a and b as the multiplicands, but adds no further semantic detail beyond what the schema's number type and requiredness already provide.

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 states the exact operation ('Multiply') on the named operands a and b, which fully specifies the tool's function. It is clearly distinct from its arithmetic siblings add, subtract, and divide.

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?

Usage must be inferred from the operation itself: an agent needing a product would select this tool. However, no explicit guidance or alternatives are named, and there are no statements about when not to use this tool.

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