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

readOnlyHint=true and openWorldHint=false already establish this as a safe, non-open read, so the bar is lower. The description adds useful return content (URL, event types, enabled flag) but omits a key behavioral fact: the signing secret is not returned here, and get_webhook_endpoint_secret exists for that.

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?

A single front-loaded sentence with no filler; the returned fields are enumerated compactly. Nothing is redundant or buried.

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 no output schema present, the description usefully summarizes the return payload, which is the right use of the space. However, for a webhook tool it should flag that the secret is excluded and route the agent to get_webhook_endpoint_secret, which is the one mistake an agent could plausibly make here.

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 0%, so the description should compensate for the lone parameter, and it does not describe it at all. Mitigating factor: there is exactly one required parameter, webhook_endpoint_id, whose name and type make its meaning self-evident, so the practical gap is small.

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?

"Read one webhook endpoint" gives a specific verb plus a singular resource, and the field list (URL, event types, enabled flag) tells the agent what comes back. The word "one" implicitly separates it from list_webhook_endpoints, but no sibling is named explicitly.

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?

Usage is only implied by the singular "one" versus the list_webhook_endpoints sibling; there is no explicit statement of when to choose this over list_webhook_endpoints or get_webhook_endpoint_secret. No prerequisites or exclusions are mentioned.

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