is_unit_fraction

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool checks a condition (numerator = 1), which implies a read-only operation, but does not disclose other behavioral traits such as error handling (e.g., for invalid inputs like zero denominator), performance characteristics, or output format. The description is minimal and lacks context beyond the basic check.

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, efficient sentence: 'Check if a fraction is a unit fraction (numerator = 1). (Domain: arithmetic, Category: egyptian_fractions)'. It is front-loaded with the main purpose, and the domain/category tags add context without redundancy. Every part earns its place, making it highly concise and well-structured.

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 low complexity (a simple boolean check), 2 parameters with no output schema, and no annotations, the description is minimally complete. It states what the tool does but lacks details on behavior, error cases, or return values. For such a simple tool, this is adequate but leaves gaps that could be addressed with more context.

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 2 parameters with 0% description coverage, but the description adds meaning by specifying that the tool checks if 'numerator = 1', clarifying the purpose of the numerator parameter. It does not explain the denominator's role beyond being part of the fraction, but since there are only 2 parameters and the description compensates for the coverage gap by defining the core logic, it merits a score above baseline.

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 explicitly states the tool's purpose: 'Check if a fraction is a unit fraction (numerator = 1).' It uses a specific verb ('Check') and resource ('fraction'), and distinguishes itself from siblings by focusing on unit fraction verification, which is unique among the many arithmetic and number theory tools listed.

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 through the domain and category tags ('Domain: arithmetic, Category: egyptian_fractions'), suggesting it's for arithmetic operations related to Egyptian fractions. However, it does not explicitly state when to use this tool versus alternatives (e.g., other fraction-checking tools like 'is_proper_fraction'), nor does it provide exclusions or prerequisites.

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