pbs_token_delete

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

With no annotations, the description fully discloses the irreversible nature and synchronous behavior. It explains the PLAN preview and return type. Lacks error condition details but is sufficient for a deletion tool.

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 relatively concise (three sentences) and front-loaded with the mutation nature. It could be slightly more streamlined but is clear and 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?

Given 5 parameters and an output schema (though not detailed), the description covers key aspects: mutation type, dry-run, execution, and prerequisites. It is complete enough for an agent to invoke correctly.

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 context for confirm (dry-run behavior) but does not elaborate on other parameters like digest or proximo_target beyond 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 tool permanently revokes a PBS API token and uses the label 'MUTATION (MEDIUM, IRREVERSIBLE)' to emphasize action and severity. It distinguishes from siblings like pbs_user_tokens_list and pbs_token_create.

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 provides explicit guidance on when to use (after listing tokens) and when not to (use pbs_token_create instead). It explains the dry-run mechanism and that confirm=True executes. It also mentions config prerequisites.

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