local_ydb_dump_tenant

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

Adds behavioral context beyond annotations: uses helper container on static network, excludes .sys objects, writes dump at specific path, and explains plan-only mode. Annotations only indicate readOnly=false, destructive=false, idempotent=false, openWorld=true, so description adds value.

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 packs substantial detail, front-loaded with the main action. Could be slightly clearer if split, but remains concise and informative.

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?

For a tool with 5 params and no output schema, description covers key behavioral aspects. Lacks mention of container dependencies or how dump is used, but sufficient for basic usage.

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 baseline is 3. Description adds minimal extra context about confirm behavior and dump path, but mostly restates schema info.

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 clearly states it dumps a configured tenant or tenant-relative path using a specific helper container, with details like excluding .sys objects and plan-only mode. It distinguishes itself from siblings like local_ydb_restore_tenant.

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?

Description explains the confirm flag for plan-only vs actual dump, but does not specify when to use this tool over alternatives like local_ydb_list_dumps or local_ydb_restore_tenant. No when-not or comparative guidance.

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