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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the write/destructive nature is covered. The description adds real value beyond them: the premium-plan entitlement requirement and the non-obvious behavior that the wildcard mirrors the first A/AAAA/CNAME record. It still omits what happens to the wildcard entry on disable.

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 compact sentences, front-loaded with the action and scoped by the example and the premium caveat. No filler.

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 two-parameter toggle with no output schema and annotations covering the safety profile, the description covers the essentials plus the premium gate and mirroring behavior. Minor gaps remain around failure on non-premium plans and the effect on existing records.

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% and both required parameters are documented in the schema, so the baseline is 3. The description's mention of the subdomain target adds only ambient context, no format or constraint detail 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?

States a specific verb (enable/disable) and resource (wildcard DNS for a subdomain), with the concrete example '*.myapp.pntr.dev' pinning down the concept. It is clearly distinguishable from siblings like toggle_subdomain, toggle_capture, and toggle_email.

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?

Usage is implied by the toggle framing and the 'Premium feature' note acts as a soft prerequisite, but there is no explicit guidance on when to use this versus adding a record directly with add_dns_record, nor any when-not condition.

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