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

With no annotations, the description carries the full burden and does so well: exact POST payload shape, signing, at-most-one-wake-per-debounce with burst collapsing, dropping wakes that would find nothing unread, one delivery attempt per wake, and auto-disable after 3 consecutive failures plus a wake.disabled inbox event. That discloses cost, failure, and state consequences an agent could not infer elsewhere.

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 is front-loaded in the first sentence, and each subsequent clause adds operational detail rather than filler. Some sentences are densely stacked (the payload, signing, and read_inbox aside in one line), which slightly hurts scanability but not correctness.

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 three-parameter configuration tool with no annotations and no output schema, the description covers what is sent, when it fires, what suppresses it, cost, failure handling, and how to inspect or revert state. An agent has everything needed to invoke it correctly and to predict side effects.

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?

Schema description coverage is 100%, so the structural meaning of url, headers, and debounce is already documented. The description still adds value by tying debounce to observable behavior (bursts start the agent once) and by naming headers such as Authorization as the mechanism for authenticating the wake. It restates the URL requirement rather than adding new constraints, which keeps it just short of a 5.

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?

Opens with a specific verb+resource framing: register a URL so RunLater starts an agent run when the inbox receives something, rather than on session open. It explicitly separates the role of set_wake (configure the hook) from read_inbox (read the events) and get_project (inspect state), so an agent can place it among 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?

Gives a clear usage context (use this instead of waiting for someone to open a session) and covers the reactivation case: after 3 consecutive failures it disables itself, and you must call set_wake again to re-enable. It also states that calling again replaces URL, headers, and debounce. It does not explicitly contrast with watch_http or schedule_http, which are the closest alternatives, so the alternatives story is incomplete.

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