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

No annotations are present, so the description carries full responsibility. It discloses the privacy risk (token visible in conversation), the account requirement, and the recovery workflow if unauthenticated. It doesn't mention reversibility or overwrite behavior, but covers the most important side effects for a secret-bearing connection tool.

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 sentences plus an access note, all substantive. Purpose is front-loaded, the security warning follows immediately, and no filler or redundant restating of schema fields.

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 tool with no output schema and no annotations, the description provides the necessary authentication context, prerequisite, and security caveat. Minor gap: it doesn't state what happens if the domain already has a Cloudflare connection, but this is not critical for initial invocation.

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 covers both parameters fully (id as Domain ID, api_token with DNS edit permissions), so baseline 3 applies. The description adds a behavioral note about token visibility but no new semantic detail about either parameter.

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?

Description states 'Connect a Cloudflare API token to a domain for automated DNS record management' – a specific verb, resource, and purpose. The Cloudflare-specific wording clearly differentiates it from sibling tools like connect_dns_provider and connect_godaddy.

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?

Gives explicit prerequisites: requires a Proof account, and provides two authentication paths (Claude Code authenticate or start_login then call again). It does not explicitly name alternative tools, but the Cloudflare-specific purpose makes selection obvious.

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