convert_bounding_box_format

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

No annotations are provided, so the description carries the behavioral burden. It discloses a payment requirement (0.005 USDC on Base L2) and the transformation scope, which is useful. However, it does not describe output structure, input requirements, error behavior, or whether the operation is stateless beyond the implied conversion semantics.

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 one tight sentence that front-loads the core purpose and format list, followed by a brief payment note. There is no redundant or filler content.

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?

The tool has no output schema and no annotations, and the payload schema is generic. The description does not provide enough detail for an agent to know what JSON fields to include, how to select the output format, or what the response looks like. This is a meaningful gap for a conversion tool that requires structured input.

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 description coverage is 100%, but the payload parameter description is a generic placeholder ('Input parameters or JSON string payload for the tool execution'). The tool description adds domain context but does not explain how to specify source format, target format, or bounding box data within the payload. Baseline 3 is appropriate because the schema nominally documents both 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 names a specific verb ('Translates') and specific resource (bounding box formats), enumerating YOLO, COCO, and Pascal VOC with coordinate definitions. This is unambiguous and distinct from sibling tools like calculate_bounding_box_3d, which address a different concern.

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 when a user needs to convert between the listed bounding box formats, but it does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions. The usage context is inferable from the purpose statement but not elaborated.

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