gpu_matrix_multiply

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

No annotations are provided. The description mentions GPU acceleration but fails to explain what 'beneficial' means (e.g., matrix size, sparsity) or disclose fallback behavior, resource usage, or error handling.

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 of 8 words, which is too terse for a tool with 3 parameters and complex GPU acceleration behavior. Essential details are omitted at the cost of brevity.

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?

Despite having an output schema (not shown), the description fails to cover parameter semantics, usage guidelines, and behavioral nuances. The tool's complexity demands more context than provided.

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 has 0% description coverage. The description does not explain any parameters: 'a' and 'b' lack shape requirements, and 'force_cpu' is undocumented despite its boolean default.

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 specifies the verb 'multiply' and resource 'matrices', and adds nuance with 'GPU acceleration when beneficial', effectively distinguishing from the sibling 'matrix_multiply' tool.

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 explicit guidance on when to use this tool versus alternatives like 'matrix_multiply'. The phrase 'when beneficial' is vague and leaves the agent to infer optimal conditions.

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