Webhooks

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral information: the response shape changes when subscription_id is passed, expanding to include recent delivery attempts. It omits how many attempts are returned or any pagination/limit behavior, which keeps it from a 5.

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 short sentences with no filler, and the conditional-mode hint arrives early. The opening is a noun fragment rather than a full statement of action, and 'its most recent delivery attempts' could be slightly more explicit about what is returned, but nothing here is wasted.

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 read-only one-optional-param listing tool with no output schema, the description covers both call modes and the debugging intent. The remaining gaps (attempt count, identifier format, returned fields) are modest given the tool's simplicity and its read-only annotations.

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 coverage is 0% and subscription_id has no schema description, so the description must carry this. It does: passing subscription_id scopes results to one subscription and adds its latest delivery attempts for debugging. That is real semantic meaning beyond the bare string type, though it leaves the expected identifier format unstated.

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 states the resource precisely ('Your webhook subscriptions') and discloses a second mode: with subscription_id it also returns the most recent delivery attempts. Combined with the verb in the name, an agent can tell this is the read/list counterpart to create_webhook. It stops short of naming or contrasting siblings explicitly, so it is clear but not fully differentiated.

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 concrete reason to supply the parameter: 'to debug a webhook that isn't arriving', which tells the agent when the diagnostic mode applies versus the plain listing mode. It does not state exclusions or point to a sibling for related tasks, so the guidance is contextual rather than complete.

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