pbs_verify_start

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

Labels as MUTATION, explains it is non-destructive by default due to dry-run, but warns of heavy I/O. Discloses async task return. With no annotations, description carries full burden and does well, though could mention permissions or lasting effects.

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?

Two sentences, no fluff, front-loaded with purpose. Every sentence adds critical information.

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 output schema exists, description adequately covers purpose, behavior, and follow-up action. References sibling tool for progress. Sufficient for an agent to select and 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 3. Description adds context for confirm parameter and links to pbs_tasks_list for progress, but does not detail other parameters beyond schema. Modest added value.

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?

Describes starting an integrity verification run on a PBS datastore with specific details: dry-run default, async task return, and progress checking via pbs_tasks_list. Clearly communicates the action and distinguishes from sibling tools.

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 that confirm=True is needed to execute. Provides guidance on monitoring progress with pbs_tasks_list. Does not exclude alternatives but offers clear context for when to use.

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