http_replay

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

With no annotations provided, the description takes on the full burden of behavioral disclosure. It clearly states that blank arguments preserve original values, supplied headers are merged, and a new history entry is logged. These are concrete side effects and merge semantics beyond what the schema reveals.

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 two sentences plus a parenthetical. It is front-loaded with the core purpose, followed by essential behavioral notes. Every sentence earns its place, with no redundant information.

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?

For a replay tool with 5 parameters and no annotations, the description covers the primary workflow: select a logged request, optionally modify fields, and understand that it logs a new entry. It does not mention return format or error handling, but an output schema exists, lowering the burden. Overall, it is appropriately complete for the tool's complexity.

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?

The input schema has 0% description coverage, so the description must add meaning. It does: 'Any argument left blank keeps the original request's value' explains the role of optional parameters, and 'Supplied headers are merged onto the original' clarifies headers_json behavior. It doesn't explicitly describe each parameter individually, but the blanket rule compensates well for the schema gap.

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 opens with 'Re-send a logged request with optional edits', which gives a specific verb and resource. The parenthetical 'Repeater tweak-and-resend' further distinguishes it from net-new send tools like http_send. This clearly conveys what the tool does.

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 establishes that this tool operates on a previously logged request (via request_id), implying it is for replay/modification rather than fresh requests. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to choose between this and sibling tools like http_send.

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