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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description adds real value by bounding the meaning of the answer: it is a worker-level readiness signal, not a statement about cache content. The remaining gap is that it never describes the shape of the answer (two booleans, one status, etc.), which matters because there is no output schema.

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 sentences, both earning their place: the first defines what is reported and the second defines the boundary of the claim. The positive statement is front-loaded ahead of the caveat.

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-argument, read-only readiness check with annotations covering the safety profile, the description is essentially complete — it says what is checked and what should not be inferred. The only omission is the return value's form, which is not covered by an output schema and is left implicit.

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 schema semantics for the description to supplement; the baseline for a parameterless tool applies. Nothing is missing on this dimension.

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: reports whether background mailbox ingestion is enabled and whether the scheduler heartbeat is fresh. That is clearly distinct from every sibling (all of which act on messages, threads, folders, or rules), so an agent can recognize this as the readiness probe 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?

The second sentence gives a clear exclusion — 'worker readiness only; it does not claim that any mailbox or thread cache is complete or current' — which steers the agent away from treating this as a cache-freshness or data-completeness check. It does not, however, name the alternative to call when the agent actually needs cache completeness or a refresh, which keeps it from a 5.

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