binary_translate

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

With no annotations, the description carries the burden alone. It does disclose a genuine behavioral trait, the policy of refusing console-specific instructions by default, but omits that the tool can write a .bin artifact to a workspace path only under a gated apply flag, and says nothing about the returned format.

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 tight sentences with the operation front-loaded and the refusal policy as a secondary clause. No filler or repetition of the tool name.

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?

No output schema and no annotations, so the description must stand in for behavior, and for a narrow translation utility it covers the core operation and the main safety behavior. The write/artifact path is left entirely to the schema, which is a modest gap but not a blocking one.

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 coverage is 67%, so most parameters are already documented structurally. The description only indirectly maps to allowUnsupported and adds nothing about hex input format or that sourcePlatform/targetPlatform are constrained enums, leaving the two undescribed enums unmentioned.

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?

Names a specific verb and resource ('Translate ... MIPS words') plus an explicit scope ('between N64 and PS2 endian representations'), which separates it from siblings like mips_disassemble or port_validate_translation. It stops short of naming any alternative tool, so it is clear but not fully differentiated.

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?

Usage is only implied: the agent must infer this is the tool for endian conversion of MIPS words rather than disassembly or validation. The clause 'unless explicitly allowed' hints at the allowUnsupported escape hatch but gives no when-not conditions or pointer to sibling tools for related tasks.

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