local_ydb_add_storage_groups

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

Annotations indicate it's a non-destructive write. The description adds behavioral context: it uses the current definition, returns a plan/rollback/targets in plan mode, and verifies after execution. No contradictions with annotations.

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 two sentences long, front-loaded with the purpose, and covers both modes without unnecessary words. It earns its place.

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 schema coverage and absence of output schema, the description provides useful workflow and output details. However, it omits prerequisites (e.g., existing pool) and error handling, leaving some gaps.

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 100% coverage with descriptions for all 5 parameters. The tool description does not add significant meaning beyond the schema, so the baseline of 3 applies.

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 increases NumGroups for a tenant storage pool using the current ReadStoragePool definition. It distinguishes from the sibling reduce_storage_groups by focusing on increase.

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 explains the two-phase workflow (plan without confirm, execute with confirm) and what to expect in each mode. It does not explicitly state when not to use the tool or list alternatives beyond the implied counterpart.

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