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

No annotations are present, so the description carries the full burden. It discloses the return content ('Returns connected account and existing Pages/Workers/zones') and clarifies it is not a founder dashboard session, indicating read-only behavior implicitly. It also explains the 'not connected' flow, which informs the agent of possible outcomes. It stops short of explicitly stating 'read-only' or describing exact response fields, but for a status check it is reasonably transparent.

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 tight paragraphs: the first states purpose, returns, and a sequencing tip; the second is a crisp routing table with three conditions. Every sentence earns its place, and the core purpose is front-loaded. No filler or repetition beyond the intentional routing recap.

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 single-parameter read-only status tool, the description covers purpose, usage, and the high-level return. Absence of an output schema is partially mitigated by naming the returned entities. The 'not connected' branch is explicitly handled. It doesn't spell out the exact response format or potential errors, but given the simplicity, it's complete enough for correct 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?

The input schema already describes companyId with context ('FreedomOS company id to act within (you must be a member)') and coverage is 100%. The tool description adds no parameter-specific detail, so it provides no value beyond the schema. Baseline 3 applies because the schema does the heavy lifting.

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?

The description opens with a specific verb 'See whether' and names the exact resource: 'standing Cloudflare deploy token in FreedomOS Vault (Pages, Workers, DNS)'. It explicitly distinguishes from 'a founder dashboard session' and states what it returns ('connected account and existing Pages/Workers/zones'). It also contrasts with sibling claim_cloudflare_preview, leaving no ambiguity about what the tool does.

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 instructs 'Use before claim_cloudflare_preview' and provides a routing decision: connected → this tool; not connected → request_connector (cloudflare) then claim_cloudflare_preview. It also warns against invoke_integration ('that stays per-send'). This is a complete when-to-use/when-not-to-use guide with explicit alternatives.

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