websex_anew

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

With no annotations, the description carries the full burden, and it does add real behavioral detail: argv-token execution with no shell parsing (a meaningful safety/invocation note) and namespace-scoped working directory. However, it omits that anew mutates files by appending/deduplicating lines, and says nothing about side effects or reversibility.

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 tight sentences with the execution model front-loaded and no filler. Slightly dense and arguably too terse on the tool's actual function, but structurally efficient.

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 for a 4-parameter tool with zero schema coverage and no annotations, the description leaves the tool's core behavior (what anew does, what it writes) and one parameter undocumented, which is a substantial gap.

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 partially does: it clarifies that 'arguments' are raw argv tokens (not shell-parsed) and that working-directory paths are relative to the engagement namespace. But the optional 'stdin' parameter is never mentioned, and engagement_id is only obliquely covered by 'engagement namespace'.

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?

It states a specific verb+resource ('Run anew from the WebSex web toolkit'), which identifies the wrapped binary but never says what anew actually does (line deduplication / appending new lines to a file). An agent unfamiliar with the binary cannot infer the tool's function from the description alone. Sibling differentiation is only by tool name, not by 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 notes it runs from the selected engagement namespace and to use relative paths for artifacts, which is context, but it gives no when-to-use guidance and no comparison to adjacent tools like websex_grep, websex_bash, or websex_execute. No exclusions or prerequisites are stated.

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