Get Cloudflare Queue

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: rows are never deleted, so results are cumulative and safe to re-poll. It omits pagination, ordering, and empty-queue behavior, which keeps it from a 5.

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?

Three short sentences, each carrying a distinct payload: what it returns, when to call it, and why it is safe to call repeatedly. Nothing is repeated from the schema or annotations and the highest-value fact (polling after a move) lands early.

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 usefully names the returned fields (per-domain status and message) and establishes append-only retention, which is what an agent needs to interpret results. It stops short of describing volume, pagination, or how terminal vs in-progress statuses are represented.

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 no parameter semantics to explain; the baseline is 4. The description correctly implies nothing must be supplied beyond the account context.

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?

Specific verb plus resource: lists Cloudflare domain-move queue rows for the account, including per-domain status and message. This is clearly not a single-record lookup, but the description does not explicitly disambiguate from the nearby get_cloudflare_domain_status or get_cloudflare_connection siblings.

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?

"Use this to poll progress after connect_domains_to_cloudflare" gives an explicit trigger and names the predecessor tool. It also covers the secondary use case (audit trail of past moves), but states no exclusions — e.g. when to prefer get_cloudflare_domain_status instead.

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