local_ydb_apply_auth_hardening

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

The description adds context beyond annotations by disclosing that the tool restarts local-ydb and behaves differently based on the confirm parameter (plan vs apply). Annotations only show readOnlyHint=false, but the description provides operational details.

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, front-loaded with the main action, then usage condition. No wasted 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?

Covers prerequisites, action, and plan vs apply mode. Lacks details about success/failure output or post-conditions, but for a tool with no output schema and clear annotation hints, it is adequate.

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?

Input schema has 100% description coverage, so baseline is 3. The description reinforces the confirm parameter's role but adds no new parameter-level semantics beyond what is already in 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 'Apply a reviewed hardened YDB config file and restart local-ydb', specifying the verb 'apply' and the resource 'hardened YDB config file'. It distinguishes from siblings like 'prepare_auth_config' by indicating this is the apply step after review.

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?

It explicitly says 'Use only after preparing and reviewing the config' and explains the confirm parameter behavior (plan-only without confirm=true). While it does not mention alternatives, the sibling names provide context that prepare_auth_config is for preparation.

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