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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered, but idempotentHint=false is unusual for a read and the description does not explain it. The wait_seconds long-polling behavior is genuine added context, yet the description says nothing about what happens on timeout, whether the wait counts against any limit, or how a non-existent or never-fired schedule is reported. Some behavioral value is added; important edges remain unstated.

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: purpose and payload first, then the waiting mechanic, then access terms. The return contents are front-loaded where an agent needs them. "No API key, no account and no sign up" is slightly promotional but does carry real access information, so it mostly earns its place.

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 only two parameters and no output schema, the main risk is the agent not knowing what comes back; the description mitigates that by naming status, attempts, HTTP status, and a response excerpt. The long-poll semantics of wait_seconds are also covered. Remaining gaps are failure and timeout behavior, which are secondary for a low-complexity read tool.

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 both parameters are fully documented with type, range, and the UUID pattern. The description's mention of "wait_seconds, up to 25" restates the schema rather than extending it, adding no format or edge-case detail. Baseline 3 is appropriate where 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 names a specific verb and resource ("Read a scheduled webhook") and goes further by enumerating what is returned: status, attempts, and post-fire HTTP status plus an excerpt of the response. That is well beyond a restatement of the name. It does not explicitly contrast itself with schedule_webhook or cancel_webhook_schedule, so sibling differentiation is left to the reader, which keeps it from a 5.

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?

It gives a clear context for use, including the specific polling pattern: pass wait_seconds to block until the status changes rather than re-calling repeatedly. Access prerequisites are stated (no API key, no account, no sign up). There is no explicit when-not guidance or named alternative, so it falls short of a 5.

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