pbs_remote_delete

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

With no annotations, the description fully discloses the mutation nature, dry-run behavior, irreversible consequences, and HTTP method. The label 'MUTATION (MEDIUM)' and detailed warnings provide complete transparency.

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 concise and well-structured: starts with purpose and risk level, then consequences, then usage instructions, then HTTP path, then a note on response. Every sentence adds value with no redundancy.

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?

Given the output schema exists, the description adequately covers the operation, consequences, and execution model. It hints at response shape but doesn't need to detail it. The tool is contextually complete for its complexity.

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 100%, so baseline is 3. The description adds no new parameter-specific information beyond what the schema already says (e.g., 'confirm=True to execute'). It does not enhance understanding of parameters.

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, using the verb 'remove'. It distinguishes from siblings by mentioning 're-create with pbs_remote_create to recover', making the purpose 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?

Explicitly states dry-run default and confirm=True to execute, and warns of consequences (sync jobs break, password lost, no rollback). However, it does not explicitly mention alternatives like pbs_remote_update for disabling, though create is mentioned.

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