local_ydb_list_dumps

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description reinforces this with 'Read-only'. It adds meaningful behavioral detail beyond annotations by explaining that only top-level dump directories containing the tenant dump folder are reported, which is useful edge behavior an agent could not infer from annotations alone.

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 compact sentences with no filler. The first sentence states the core operation and scope, and the second provides the usage context and an important filtering behavior. Every clause 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?

For a low-complexity read-only list tool, the description covers what it lists, how it filters dumps, and when to use it. There is no output schema, so a slightly more explicit return format would be ideal, but the phrase 'list of available tenant dumps' plus 'choose a dumpName' gives enough for an agent to select and invoke it correctly.

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 already documents both parameters with 100% coverage, including defaults and failure behavior. The description adds the context that dumps live under profile.dumpHostPath, but it does not add new parameter-level semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 uses a specific verb ('list') and a specific resource ('available tenant dumps under profile.dumpHostPath'), and further clarifies exactly what counts as a dump. It clearly differentiates the tool from siblings like restore_tenant or dump_tenant by framing it as the read-only selection step before restore.

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 when to use the tool: 'Use before restore to choose a dumpName'. It gives clear operational context, though it does not explicitly name alternative tools to avoid or discuss when not to use it.

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