Run Garbage Collection

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

Annotations already indicate readOnly=false, idempotent=false, and destructive=false. The description adds the useful detail that the tool returns a task UPID that can be tracked, but it does not disclose potential side effects of garbage collection (e.g., deletion of unreferenced data) or prerequisites. This adds some context but not rich behavioral disclosure.

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, front-loaded with the purpose, and followed by simple Args and Returns sections. Every sentence adds value, and there is 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?

For a single-parameter tool with annotations and no output schema, the description covers the purpose, the parameter, and the return value, including a tracking hint. It could be more complete by explaining what garbage collection does or when to run it, but the tool is simple and well-specified enough for an agent to use 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?

The input schema has one parameter 'store' with the description 'Datastore name,' and the description repeats the same information in the Args section. Since schema coverage is 100%, the description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 states 'Start a garbage collection job on a datastore,' clearly identifying the verb (start) and resource (garbage collection job). This distinguishes it from sibling run tools like pbs_run_verify and pbs_run_sync_job, which perform different operations.

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 gives clear context: this tool is for starting a GC job on a datastore, and it notes that the returned UPID can be tracked with pbs_get_task_status. It does not explicitly exclude alternatives or state when not to use, but the purpose is unambiguous given the sibling tool names.

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