pbs_node_subscription_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 type (MEDIUM), local storage, dry-run behavior, execution with confirm=True, HTTP endpoint, return format, and reversibility. This is comprehensive.

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 (5 sentences) with key information front-loaded: purpose, then behavior, then return, then reversibility, then config. Every sentence adds value without 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 presence of an output schema (though not shown), the description adequately explains the dry-run and execution cases. It also mentions config requirements. No missing critical context.

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% and each parameter has a clear description. The description adds context like the default value for node ('localhost') and the return format on execution. It does not add much beyond schema, but the schema itself is sufficient.

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?

Description clearly states the action: 'delete the locally-stored subscription info on a PBS node'. The verb 'delete' and resource 'subscription info' are specific. Sibling tools like pbs_node_subscription_get and pbs_node_subscription_set confirm distinct purpose.

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?

Provides explicit guidance: dry-run by default, confirm=True to execute, and reversibility via pbs_node_subscription_set. Also notes need for PROXIMO_PBS_* config. This helps the agent decide when to use and what alternatives exist.

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