local_ydb_add_storage_groups

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

Annotations already indicate mutation. Description adds value by detailing dry-run return (plan, rollback) and post-execution verification, which are not implied by 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?

Single sentence, concise, front-loaded with purpose. No extraneous 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?

Fairly complete for a tool without output schema: describes return values (plan, rollback, targets) and verification step. Lacks error scenarios or precondition details, but covers core behavior.

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?

All 5 parameters have schema descriptions (100% coverage). The tool description does not add significant semantic detail beyond the schema, but re-emphasizes the confirm parameter's role in execution.

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?

Description states specific action: increase NumGroups for a tenant storage pool. Distinguishes from sibling 'local_ydb_reduce_storage_groups' as the opposite operation.

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?

Describes dry-run vs execution behavior (confirm=true). However, lacks explicit guidance on when to add vs reduce storage groups and does not mention prerequisites or context for choosing this tool over alternatives.

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