calculate_gcd_lcm

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

No annotations provided. Description mentions Euclidean algorithm and return format but fails to disclose potential limitations, error handling, or behavior with non-positive integers. Minimal value added beyond schema.

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 with key info front-loaded. Second sentence useful for discoverability. Could be more compact but no redundancy.

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 basic purpose and return structure, referencing output schema. Missing edge cases (e.g., negative numbers, zero) and error scenarios, which limits completeness for a simple math 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?

Input schema describes both parameters ('First integer', 'Second integer'), achieving 100% coverage. Description adds no additional semantic meaning beyond the schema.

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?

Clearly states it calculates GCD and LCM of two integers using Euclidean algorithm, with return format specified. However, distinction from other math calculators is weak despite reference to related 'math' calculators.

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?

Implies usage for GCD/LCM calculations but lacks explicit guidance on when to use this tool over alternatives. No exclusions or context provided.

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