pbs_remote_delete

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

No annotations provided, so description carries full burden. It discloses mutation, destructive effects, dry-run behavior, no rollback, and impact on sync jobs. Also provides HTTP method and path. Comprehensive for a deletion 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?

Description is concise and front-loaded with 'MUTATION (MEDIUM): remove a PBS remote...' and uses efficient phrasing. However, the last line 'Smoke-confirm: response shape on success.' is somewhat vague and could be omitted or clarified.

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?

Despite no annotations, the description covers the tool's behavior thoroughly: dry-run, confirmation, post-deletion effects, no rollback, recovery path, and HTTP endpoint. Complete for a delete tool with output schema present.

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 33% with only proximo_target described. Description adds context for confirm ('confirm=True to execute') and implies name via HTTP path, but does not explain name or proximo_target beyond schema. Adds some value but not fully compensating.

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 tool removes a PBS remote and its stored credentials, with specific verb 'remove' and resource. It distinguishes from siblings like pbs_remote_create, pbs_remote_get, pbs_remotes_list, and pbs_remote_update by its destructive nature.

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?

Explicitly mentions dry-run by default and requires confirm=True to execute. Describes consequences (sync jobs break, password re-supply needed, no rollback) and recovery via pbs_remote_create. Provides clear when-to-use and implications.

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