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

Annotations already cover read-only and idempotency, but the description adds non-obvious traits: warnings do not block scheduling yet will make every send fail, and must always be relayed; blocking vs non-blocking checklist items gate sending. This is exactly the kind of failure-mode context structured fields cannot express.

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?

Purpose and the 'call FIRST' rule are front-loaded, and the return shape is summarized before the routing instructions. It is dense and slightly run-on with stacked parentheticals, but nearly every clause carries actionable routing or failure information.

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 zero-parameter readiness probe with no output schema, the description supplies everything needed: the return shape, the meaning of warnings vs blocking items, the per-item fields, and the ordering constraint relative to send_broadcast. Nothing an agent needs to call it correctly is missing.

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 does clarify the response payload ({ about, ready, checklist, summary, warnings }) and the shape of checklist items, which aids invocation interpretation even though no input semantics are needed.

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 concrete verb and object: 'Check whether this workspace is set up to send real broadcasts, and what is still missing.' This is clearly distinct from siblings like account_status, whatsapp_status, and preview_broadcast, and an agent can identify it without opening a 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 says to call it FIRST for send/schedule requests on new or unfamiliar workspaces, and again for greetings, 'what is DripRaven', or just-connected cases. It also states the negative condition — do NOT call send_broadcast when ready is false — and names the recovery path (walk through each not-done blocking item via next_tool and instructions).

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