domains_schedule_ns_check

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

Annotations already declare destructiveHint=true, idempotentHint=false, openWorldHint=true and readOnlyHint=false, so the safety profile is known, but the description adds nothing else. It doesn't say what gets scheduled or overwritten, whether the check is async, whether it consumes quota, or what permissions are needed – for a destructive, non-idempotent mutation that is a real gap.

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?

It is short, but it isn't really a description – a bare title fragment followed by a raw HTTP verb and path. It is front-loaded with a redundant restatement rather than a purpose statement, so the brevity comes from under-specification rather than disciplined editing.

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 destructive, non-idempotent, open-world mutation with one undocumented parameter and no output schema, the description supplies none of what an agent needs: no outcome of the call, no state change, no return value, and no failure conditions. Contextual completeness is essentially absent.

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?

There is one required parameter, id, at 0% schema description coverage. The path template only implies it's a domain identifier; the description says nothing about which domain ID (zone vs registration id), the expected format, or whether it must be numeric (schema says number). Almost no meaning is added beyond 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 text only restates the tool name as the title 'Domains schedule ns check' and repeats the HTTP endpoint 'POST /domains/{id}/schedule-ns-check'. A reader can guess that it schedules a nameserver check for a domain, but the description doesn't say that in prose, doesn't explain what a 'ns check' verifies, or differentiate it from siblings like domains_verify or domains_check_domain_delegation.

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?

There is no guidance on when to use this tool, when not to, or which sibling performs a similar check (domains_verify, domains_check_domain_delegation, domains_get_expected_nameservers). The endpoint path is the only context and it doesn't route an agent among alternatives.

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