reverse_complement

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

No annotations are provided, so the description must convey behavioral traits. It only states the operation but does not disclose whether the function is idempotent, what metadata is included in the return, or any potential side effects. This is insufficient for an agent to understand the tool's behavior fully.

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 concise—two sentences plus an args/returns section. However, it packs little information, making it under-specified rather than efficiently informative. It does not waste words but also fails to provide necessary detail.

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 is simple with one parameter and an output schema, the description is incomplete. It does not explain the return value beyond 'dictionary containing reverse complement and metadata,' leaving the agent unaware of the dictionary structure or possible keys.

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?

With 0% schema description coverage, the description must compensate. However, it merely restates the parameter name and type ('sequence: DNA sequence string'), adding no additional semantics such as expected format (e.g., uppercase, no spaces) or constraints.

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 purpose: 'Get the reverse complement of a DNA sequence.' This is a specific verb+resource combination that distinctly identifies the tool's function. It is easily distinguishable from sibling tools like transcribe_dna, translate_sequence, or calculate_gc_content.

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 provides no guidance on when to use this tool versus alternatives. With multiple related tools (e.g., transcribe_dna, translate_sequence) available, an agent receives no help in selecting the correct tool for the task.

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