paserver_remove

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

With no annotations, the description carries the full burden. It discloses the remote deletion behavior and warns about wildcard dangers, but does not explicitly state that deletion is permanent and irreversible. This is a meaningful gap for a destructive operation.

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 tight and well-structured: purpose first, then a clarifying note, usage guidance, a warning, and a formatted argument list. Every sentence adds value, and nothing is redundant.

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 purpose, usage, warnings, and parameter semantics. Since an output schema exists (per context signals), return value details are not required. The only omission is an explicit note on irreversibility, but the wildcard warning partially covers safety. Overall, it is complete for a delete operation.

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%, so the description must explain each parameter. It does so concisely: profile, remote_path (with wildcard note), timeout (with default), and studio_root (optional). This fully compensates for the lack of schema descriptions.

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 states the verb 'Delete' and the resource 'a file or directory on the PAServer remote host', distinguishing it from sibling tools like paserver_get and paserver_put. It also clarifies that the `-R` flag targets the remote host, not the local cache, making the intent unambiguous.

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 provides explicit use cases ('clean up scratch dirs or old deployments') and a caution about wildcards. It clarifies remote vs. local operation, but does not explicitly name alternative tools for local deletion or other actions, though none are obvious siblings.

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