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

No annotations are provided, so the description carries full burden. It only states the algorithm and return structure but fails to disclose behavioral traits like determinism, side-effect safety, or handling of negative integers, which is minimal for a simple calculation.

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 efficiently short, with one main sentence and a minor note about list_bundles. However, the second sentence is somewhat tangential and could be removed for tighter focus.

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?

Given the tool's simplicity and existence of an output schema, the description covers the basics adequately. However, it lacks examples or contextual advice on when to use it among many sibling calculators, which would improve completeness.

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% with clear parameter descriptions ('First integer', 'Second integer'). The description adds no additional meaning beyond restating that it takes two integers, so it meets baseline without enhancement.

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 states it calculates GCD and LCM of two integers using Euclidean algorithm, with a specific verb and resource. It effectively distinguishes itself from many sibling 'calculate_' tools due to its specific mathematical function.

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 implies usage for computing GCD/LCM but lacks explicit when-to-use or when-not-to-use guidance. It mentions related math calculators via 'list_bundles' but does not provide clear alternatives or exclusion criteria.

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