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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds real value beyond them by naming the required permission and roles and by stating what is returned (active flag, last success/failure). It says nothing about result volume or pagination, which is the remaining gap.

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 tight sentences, front-loaded with what is listed, followed by the return content and then the permission/parameter facts. Every clause carries information an agent would otherwise have to infer.

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 an output schema present, the description needn't detail return shapes, and annotations cover the safety profile. What remains — permission requirements, workspace defaulting, and which fields matter — is all stated, so an agent can call this correctly without further reading.

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 100% and the workspaceId description already explains the id source and cross-workspace id hazard. The description still adds the useful default rule ("the current one unless workspaceId names another") and confirms it is the only, optional parameter.

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 ("List the webhook endpoints registered for the workspace") and even enumerates the returned fields (active status, last success/failure). The list-vs-single distinction against get_webhook is implicit rather than named, so it falls just short of explicit sibling differentiation.

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 clear operating context: it needs webhooks.read (held by Admin, Editor, Viewer) and takes only the optional workspaceId. It does not explicitly say when to prefer get_webhook or list_posts-style alternatives, but for a simple enumerator the applicable conditions are covered.

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