port_validate_translation

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

With no annotations, the description carries the full burden, and it does disclose one real behavioral guarantee: validation is exact round-trip only, not semantic. That is genuine added context. But it says nothing about whether the operation is read-only or mutating, what the return value looks like, whether mismatches raise errors or return a result, or any cost/limit.

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?

A single tight sentence with the scope statement front-loaded and the key exclusion trailing. Nothing redundant.

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?

Three required parameters with zero schema documentation, no annotations, and no output schema, in a tool whose result format (pass/fail vs. failing offset) materially affects how an agent uses it. The description cannot answer how to interpret a failure or what to pass in hex without inference.

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 0%, so the burden falls on the description, which mentions none of the three parameters. The names hex, sourcePlatform, and targetPlatform are largely self-explanatory and the two platform parameters are enum-constrained, which limits the damage, but the hex encoding format, byte order, and whether source and target may be identical all remain unstated.

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 ('Validate') and a specific resource ('supported N64/PS2 encoding translation round-trips'), and adds a boundary clause distinguishing it from semantic-equivalence checking, which separates it from equivalence_record/compare_functions. It stops short of naming a sibling outright, so the differentiation is implied rather than explicit.

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 clause 'this is not a semantic equivalence proof' implies when this tool is the wrong choice for proving behavioral equivalence, which is useful routing information. However, there is no positive guidance on when an agent should reach for this versus binary_translate, equivalence_record, or texture_decode_n64/ps2, and no stated prerequisites.

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