conversion_bcd

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

No annotations are provided, so the description carries the full burden. It only states conversion functionality but does not disclose behavioral traits such as input validation, error handling, or potential side effects. Minimal 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 short and to the point, with two sentences covering purpose and a pointer to further guidance. No unnecessary words, though the pointer could be integrated more efficiently.

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 4 required parameters and no output schema, the description should at least clarify parameter roles. It does not, leaving the agent without enough context to invoke the tool correctly. Also lacks return value information.

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 4 required parameters with no descriptions (0% coverage). The description does not explain the meaning or expected values of parameters like mode, outputFormat, or inputFormat. It adds no value beyond the schema.

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 is a BCD Converter that converts between BCD and decimal numbers, with encode and decode operations. It distinguishes itself from sibling conversion tools like conversion_base_converter or conversion_binary_decimal by specifying the exact format.

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 only mentions using describe_tool for full guidance, providing no context on when to use this tool versus alternatives like conversion_binary_decimal or conversion_number_base. It lacks explicit usage context or exclusions.

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