websex_http_repeater

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

With no annotations, the description carries the full burden. It usefully discloses that scope is enforced, that persisted headers/cookies/match-replace rules are applied, and that evidence is retained — real behavioral context. It omits side-effect/mutation risk, prerequisites (e.g. session must already exist), and rate/authorization constraints.

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 dense sentences, zero filler; the core action is front-loaded and each clause earns its place by adding scope, persistence, and evidence 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?

An output schema exists, so return values need not be explained. The description covers the operation's behavior and session/scope model adequately, but with 0% schema coverage and 6 parameters, it could say more about how the required engagement_id/session_id relate and what happens on scope rejection.

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% across 6 parameters, so the description must compensate. It clarifies the engagement/session relationship and the request parts (method, url, headers, body) conceptually, but gives no format, default, or constraint detail for any individual parameter.

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?

States a specific verb and scope: 'Replay one crafted HTTP request through an engagement workbench session.' An agent can tell this is a single-request replay rather than a bulk/fuzz tool, but the description never names or contrasts with WebSiblings like websex_http_request or websex_http_intruder.

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 implied by 'one crafted HTTP request' within a session, hinting at single-shot manual replay versus an intruder's many-request fuzzing. However there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance.

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