calculate_roman_numeral

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

No annotations are provided, and the description discloses only the basic conversion and return format. It does not clarify that it likely converts only decimal to Roman (given the integer input), nor does it mention error handling or performance. The schema's min/max constraints cover range limits, so no contradiction.

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: the first clearly states the purpose and return format, the second points to related tools. No wasted words, front-loaded, and appropriately sized for the tool's simplicity.

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 presence of an output schema (implied) and the tool's simplicity, the description covers the core function. However, it could be more complete by explicitly stating that conversion is from decimal to Roman (or clarifying bidirectionality). The completeness is high but not perfect due to this minor gap.

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 provides 100% description coverage for the parameter 'value' with 'Decimal number to convert to Roman numeral'. The description adds no additional meaning beyond the schema, so it meets the baseline with no extra value.

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 verb 'convert' and the resources 'Roman numerals and decimal' with range '1-3999', and specifies the return format. However, it implies bidirectional conversion while the input schema only accepts an integer, suggesting only decimal-to-Roman conversion, which introduces minor ambiguity.

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 mentions 'See list_bundles for related conversions calculators', providing a pointer to alternatives, but lacks explicit guidance on when to use this tool versus siblings like convert_angle or convert_temperature. Usage context is implied by the tool name rather than explicitly stated.

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