local_ydb_create_tenant

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

The description discloses the dry-run behavior (without confirm=true returns plan only) and confirms the creation action. Annotations provide idempotentHint=true, which is consistent. It adds value beyond annotations by specifying the precondition and plan mode, but could elaborate on error handling or side effects.

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?

Two concise sentences that front-load the purpose and immediately provide usage guidance. No extraneous information; every sentence serves a clear function.

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 parameter count and lack of output schema, the description covers the essential behaviors: creation precondition, plan mode, and ordering with sibling tools. It could be more complete by describing the output format or success/failure signals, but it is adequate for the tool's complexity.

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 the base is 3. The description adds value by explaining the confirm parameter's behavior (plan vs. execute), which is not fully captured in the schema description. It reinforces the role of profile and configPath without adding much new information.

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 creates a CMS tenant when the static node is running, using specific verbs and resources. It distinguishes itself from siblings like local_ydb_start_dynamic_node by explaining the ordering dependency.

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 explicitly states the usage context (before local_ydb_start_dynamic_node for tenant topologies) and explains the confirm parameter's role in plan vs. execution. It provides clear when-to-use guidance, though it does not list explicit when-not-to-use scenarios.

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