cloudflare_dns_import

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

Mentions multipart/form-data encoding, but lacks details on side effects (overwrite/append), validation, or errors. No annotations to supplement.

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 core action. No extraneous information.

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?

Adequate for a simple import tool, but lacks details on behavior (e.g., duplicate handling, response structure) which could help given no output schema.

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?

Adds context beyond schema: specifies file format (BIND) and encoding (multipart/form-data), which helps the agent prepare the request correctly.

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?

Clear verb (Import) and resource (DNS records) with specific input format (BIND zone file). Distinguishes from siblings like create (single) and export.

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?

Implied usage for bulk import from a BIND file, but no explicit when-to-use, when-not-to-use, or alternatives like cloudflare_dns_create.

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