websex_httpie

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

With no annotations, the description carries the full burden and does disclose genuinely useful behavior: argv tokens are executed directly and shell parsing is never used, which tells the agent that pipes, redirects, and metacharacters will not work. It also states the execution context (engagement namespace) and working-directory convention. It does not mention permissions, network egress constraints, or whether requests are logged/recorded.

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-loaded with what the tool is and how execution works, then the scoping/path guidance. No filler, though the namespace/path sentence could be tightened.

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 described. However, for a request-emitting tool with zero annotation coverage, the description omits auth/credential handling, network constraints, and the meaning of the undocumented stdin parameter, leaving gaps an agent may need to guess at.

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 4 parameters, so the description must compensate. It clarifies 'arguments' (raw argv tokens, not a shell string) and implicitly the engagement namespace and relative working directory, but the 'stdin' parameter and the exact form of engagement_id are never addressed.

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 names a specific tool (httpie/http) and a specific runtime (the WebSex web toolkit container), so the agent knows this is a CLI wrapper rather than a native HTTP client. It is less explicit about how it differs from siblings like websex_curl or websex_http_request, but the 'runs `http` directly with argv tokens' phrasing is distinctive.

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 gives operational hints ('use relative paths for engagement artifacts', 'runs from the selected engagement namespace') but never states when to choose httpie over websex_curl, websex_http_request, or websex_bash. No prerequisites or exclusions are given, so routing among the many HTTP-capable siblings is left to inference.

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