calculate_fraction

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

With no annotations, the description carries full burden. It only states the operations and return format, omitting any behavioral traits such as side effects, permissions, error handling, or constraints like denominator zero. This is minimal disclosure.

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 two sentences long, front-loaded with purpose, and contains no superfluous information. Every sentence is meaningful and contributes to understanding.

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 the existence of an output schema, the description is adequate but has gaps. It lacks usage guidelines, edge-case handling (e.g., denominator zero), and differentiation from sibling tools beyond a generic reference. It does not explain default parameter values.

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 coverage is 100%, so the schema already documents parameters. The description lists the supported operations (matching the operation enum) and specifies the return format, adding some value beyond schema. However, it does not provide additional parameter details like defaults or behavior for optional parameters.

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 the tool performs fraction operations (add, subtract, multiply, divide, simplify), using a specific verb and resource. It distinguishes from other calculators by focusing solely on fractions and mentioning related tools via list_bundles. The return format is also specified.

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 implicitly suggests when to use the tool (for fraction operations) and references list_bundles for related calculators, but does not explicitly state when not to use it or how it differs from siblings. No exclusions are provided.

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