local_ydb_restore_tenant

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

Annotations indicate destructiveHint=true and readOnlyHint=false, consistent with 'restore'. The description adds valuable context by explaining that without 'confirm=true' the tool returns a plan and does not write data, which is a key behavioral trait beyond 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, each serving a purpose: the first states the core action, the second provides usage guidelines and explains the confirm parameter. No superfluous 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?

Given no output schema, the description covers return behavior for dry-run mode but does not detail output for the actual restore. However, the usage context (after bootstrap/rebuild) is given, and the key parameter behavior is explained. Adequate for a restore tool.

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% and each parameter has a description in the schema. The description adds minimal extra meaning, only linking 'confirm' to the plan behavior. It does not provide additional details about 'dumpName' or 'configPath' beyond the schema.

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 restores a tenant from a dump, with a specific verb ('Restore') and resource ('configured tenant'), and distinguishes from siblings like 'local_ydb_dump_tenant' by specifying the direction (restore vs dump).

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 says 'Use after bootstrap or rebuild when the target tenant is ready', providing clear context. It also explains the dry-run behavior without 'confirm=true'. However, it does not explicitly state when not to use or list alternative tools.

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