port_write

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

The annotations only declare readOnlyHint=false, and the description confirms this is a write. Beyond that, it does not disclose safety implications, unsupported ports, error behavior, reversibility, or side effects. For a low-level hardware write operation, this leaves important behavioral context missing.

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?

Three short sentences front-load the core action, then specify width and use cases. There is no filler, and the structure lets an agent quickly identify purpose and applicability.

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?

There is no output schema and annotations are sparse, so the description carries most of the contextual burden. Given the risk and complexity of hardware I/O writes, it should include cautions, expected effects, or failure behavior, but it does not.

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%, so the schema already documents port range, value, and width semantics. The description repeats the width meaning but does not add format, constraint, or edge-case details beyond the schema, making the baseline 3 appropriate.

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 gives a specific verb and resource: 'Write to an x86 I/O port.' This clearly distinguishes the tool from the sibling port_read and from memory-writing tools such as mem_write. Width and concrete hardware use cases add further specificity.

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?

It names concrete contexts for use ('Mode X unchaining, Hercules graphics, hardware config'), which implies when the tool is appropriate. However, it does not say when not to use it, nor does it point to alternatives like port_read or mem_write for related operations.

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