Get Cloudflare Connection

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

Beyond the readOnly/idempotent annotations, it discloses the key operational trait an agent could not infer: the connect step is a human browser action bound to the Porkbun web session, so polling is the only API path. It also names the response field (connectUrl) that drives the next loop iteration.

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 purpose in one clause, then escalates to the non-obvious constraint (human action) and the polling protocol. Every sentence carries actionable instruction; nothing is 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?

With no output schema, the description compensates by naming the two fields that matter (connected, connectUrl) and describing the state machine around them. An agent has everything needed to call it and to act on its result.

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 there is nothing to disambiguate and the baseline of 4 applies. The description correctly spends no words restating an empty 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 and resource ('check whether this Porkbun account is connected to a Cloudflare account') and immediately differentiates it from the mutating siblings connect_domains_to_cloudflare and disconnect_cloudflare by declaring it a read-only status check. An agent can select it without opening the schema.

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 labels itself 'the POLL TARGET for the connect flow' and gives a full when-to-use sequence: show connectUrl, ask user to authorize, re-call every few seconds until connected is true. It also names the exclusion — connecting cannot be driven over the API.

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