calculate_roman_numeral

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

No annotations are provided, so the description must carry the full burden. It only states the basic function and return type, without disclosing error handling, edge cases, or any side effects. This is insufficient for full transparency.

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 extremely concise: two sentences that front-load the purpose and output, with a brief redirection to related tools. Every word adds value.

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, the description covers the core functionality and output structure. The output schema likely provides additional return details. The description could explicitly mention the valid range, but that is already in the schema.

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 already describes the parameter with high coverage (100%). The description adds no new semantic details beyond restating its purpose; it does not clarify the bidirectional ambiguity or provide format expectations.

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 action ('Convert between Roman numerals and decimal') and the range (1-3999). It distinguishes itself from sibling tools by its specific domain (Roman numeral conversion) and mentions a related bundle. However, 'between' implies bidirectional conversion, but the input schema only accepts a decimal integer, so it is slightly misleading.

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 includes a pointer to 'list_bundles' for related 'conversions' calculators, which helps users find alternatives. However, it does not explicitly state when to use this tool versus other similar tools or provide any prerequisites or context.

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