edit_dns_subdomain

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the pdns/edit permission requirement, useful auth context, but says nothing about partial vs full update semantics, reversibility, or what the required 'confirm' flag guards against.

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 short sentences, front-loading the action and then the permission prerequisite; nothing is wasted. The garbled character encoding hurts readability but not structure.

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 mutation tool with no output schema, the description covers the action and the auth requirement, and the schema carries all parameters. It omits what an edit actually changes (full replacement vs patch) and any confirmation behavior, so it is adequate but not complete.

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 description coverage is 100%, so the three parameters are already documented at the schema level and the description correctly needn't repeat them. It adds no syntax or constraint detail beyond the schema, so baseline 3 applies. (Descriptions are mojibake-encoded, which limits their real usability, but that is a schema issue, not a description gap.)

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?

States a specific verb and resource ('Обновить сабдомен' = update subdomain) and even names the backing endpoint (pdns/edit_subdomain), so the agent can distinguish it from add_dns_subdomain/delete_dns_subdomain. It does not explicitly name those siblings or state which fields are editable, so it falls short of a 5.

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?

'Требует права pdns/edit' gives a real precondition (required permission), which is more than nothing. However there is no when-to-use vs when-not guidance and no mention of the sibling subdomain tools, so usage is only implied.

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