pbs_datastore_create

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

With no annotations, the description fully discloses behavioral traits: mutation, medium severity, dry-run default, async UPID with 'submitted' outcome, no rollback, and endpoint. Warns about path conflict.

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?

Concise and well-structured: categorical label, dry-run note, async note, rollback note, confirm instruction, endpoint, and parameter hints. No wasted words.

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?

Adequate for behavioral context (async, dry-run, no rollback) but incomplete on parameter details. Output schema exists, so return values are not needed, but the low parameter coverage hurts completeness.

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 description coverage is only 13% (low). The description only hints at optional parameters like gc-schedule, prune-schedule, notification-mode, but does not explain the required name and path or other parameters. Insufficient compensation.

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 action ('create') and resource ('new PBS datastore at the given path'), distinguishing it from sibling tools like update, delete, list, and get.

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 clear usage context: dry-run by default, confirm=True to execute, async nature, no rollback, and path conflict warning. Does not explicitly state when not to use, but the context is sufficient.

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