Get Cloudflare Connection

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

Annotations already declare it as a safe, idempotent, read-only, non-open-world call, and the description adds the crucial non-obvious behavior: authorization is bound to the web session and cannot go over the API, plus the polling contract and the connectUrl fallback. This is well beyond what the annotations convey.

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?

Front-loads the core purpose and the poll-target role, then adds the human-action caveat and the loop. Slightly dense but every sentence carries operational weight; 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?

No output schema exists, yet the description explains the key return values and the state machine (connected false → connectUrl → poll). For a zero-parameter read tool this covers everything an agent needs to call it correctly.

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 tool takes zero parameters, so the baseline is 4. The description goes further by describing response fields (connected, connectUrl) and the conditional when connectUrl is present, which is useful though not strictly a parameter concern.

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 and resource ('Check whether this Porkbun account is connected to a Cloudflare account, and which one') and immediately identifies its role in the larger connect flow. It is clearly distinguishable from siblings like disconnect_cloudflare and connect_domains_to_cloudflare.

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?

Explicitly frames itself as 'THIS IS THE POLL TARGET for the connect flow', states when connecting is not API-drivable (human browser consent), and prescribes the exact loop: show connectUrl, ask user to authorize, re-call every few seconds until connected is true. Also notes everything else is automatable downstream.

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