neuron_replay_request

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

With no annotations provided, the description carries the full burden. It usefully discloses that the request runs in the service worker context, inherits browser cookies/session, and that response bodies are truncated at 50KB. However, it does not mention the potentially mutating/side-effecting nature of re-firing requests (e.g., POST/DELETE can change server state), which is a meaningful transparency gap.

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 short, front-loaded with the core action, and each sentence earns its place: the mechanism, the modification capability, the Postman analogy, and the response truncation limit. No fluff.

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?

The description covers the key context an agent needs for invocation, including the session behavior and truncation limit, and the schema covers parameter definitions. However, there is no output schema and the description does not specify the response format beyond truncation, leaving the agent uncertain about what the tool returns (status, headers, body shape, etc.).

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 already covers all four parameters with descriptions, so baseline is 3. The description adds that method, headers, and body can be modified before sending, but this is still just a partial restatement of schema capabilities and does not add deeper semantics like accepted header formats or body encoding.

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 identifies the action ('Re-fire an HTTP request'), the resource (an HTTP request), and the execution context (service worker with browser cookies/session). It also distinguishes itself from sibling tools by emphasizing live-session replay with modification capability.

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 gives clear context: use this when you need to resend a request using the live browser session, like Postman but with session cookies. It does not explicitly name sibling alternatives or state when not to use it, but the tool's purpose is well-scoped enough for an agent to infer appropriate use.

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