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

Annotations already indicate this is a write operation (readOnlyHint=false) with destructive intent (destructiveHint=true), and the description does not contradict them. However, the description adds no behavioral context beyond what the annotations provide, such as side effects, permissions, or idempotency.

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 extremely short but this is under-specification, not conciseness. It repeats the title verbatim and contains no structured information, wasting the opportunity to add useful content.

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?

This tool has a nested body object, multiple required fields, and no output schema, so the description must provide substantial context. It provides none, leaving agents completely uninformed about the purpose or expected behavior.

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 schema description coverage is 0%, so the tool description must compensate for the lack of parameter explanation. The description mentions no parameters at all, leaving the agent with no additional meaning beyond the raw schema field names and generic property 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 'Create specific handle - Create specific handle' is a direct repetition of the title and provides no additional specificity. It does not explain what a handle is, what 'specific' means, or how it differs from sibling create tools like createUser or createDnsZone.

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?

No guidance is given on when to use this tool versus alternatives. The description lacks any mention of use cases, prerequisites, or exclusions, and does not reference any sibling tools.

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