websex_curl

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 curl runs directly with argv tokens and that shell parsing is never used, plus the engagement namespace scoping. It omits auth requirements, rate limits, and error/failure behavior, leaving notable gaps for a command-execution tool.

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 compact sentences, front-loaded with the core action, then the execution model, then the working-directory convention. Little waste, though the namespace/path sentence could be tighter.

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. But the description omits the stdin parameter and gives no tool-selection context against its many HTTP siblings, leaving the definition only minimally complete for a 4-parameter execution tool.

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 coverage is 0%, so the description must compensate. It conceptually maps 'arguments' (argv tokens), 'engagement_id' (engagement namespace), and 'working_directory' (relative paths), but says nothing about the 'stdin' parameter, so one of four parameters remains undocumented in both schema and description.

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 ('Run curl') and resource ('curl'), and clarifies it is the WebSex web toolkit variant. However, it does not differentiate itself from close siblings like websex_http_request or websex_httpie, which an agent must choose between.

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?

No indication of when to prefer this over websex_http_request, websex_httpie, or websex_bash. The only guidance ('use relative paths for engagement artifacts') is a path convention, not a tool-selection rule, so the agent is left to infer the use case.

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