pbs_datastore_create

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

With no annotations provided, the description carries full burden. It discloses key behaviors: dry-run default, async worker task, no rollback, additive nature with potential path conflict, and outcome='submitted'. It could be more explicit about error conditions or permissions, but overall very transparent.

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 front-loaded with the purpose and severity. It efficiently packs essential details without excess. A slightly more structured layout could improve readability, but it's already well-organized.

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 tool's complexity (mutation, async, dry-run), the description covers behavioral aspects well. It references related tools and mentions the output nature. Since an output schema exists, return value details are not required. Minor omission: error handling or required permissions could be added.

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 parameters are documented. The description adds meaning by explaining confirm's role (dry-run vs execution), hints about naming quirks for gc_schedule, prune_schedule, notification_mode, and the function of proximo_target.

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 explicitly states 'create a new PBS datastore at the given path', with a clear verb and resource. It distinguishes from siblings by focusing on creation, while siblings like pbs_datastore_delete, update, list cover 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 details when to use the tool: it advises checking for collisions with pbs_datastores_list beforehand and suggests using pbs_datastore_update for modifications. It also explains the dry-run default and how to execute with confirm=True.

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