local_ydb_restart_stack

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

The description details the sequence of actions (stopping both dynamic and static containers, then starting static node, ensuring tenant, then dynamic node) and explains the confirm flag's effect (dry-run vs execution). This adds valuable behavioral context beyond the annotations, which only indicate non-read-only and non-idempotent.

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: the first lists the steps of the restart process, the second provides usage guidance. Every part is informative and there is no redundant 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?

Given the tool's parameters are all documented and no output schema exists, the description adequately covers the tool's behavior, including the plan-only mode. It provides enough context for the agent to understand the restart sequence and when to use it.

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 three parameters are fully described in the input schema (100% coverage). The description adds meaning to the confirm parameter by explaining its role in plan-only output versus execution, which is useful beyond schema descriptions.

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 restarts a selected profile by enumerating the steps (stopping containers, starting static node, ensuring tenant, starting dynamic node). It is specific about the resource (profile) and action (restart), and distinguishes from sibling tools like start_dynamic_node or create_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?

The description explicitly says 'Use after config or runtime changes' and explains the behavior of the confirm parameter, providing clear context on when to use. It does not explicitly list when not to use or alternative tools, but the sibling list provides implicit differentiation.

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