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

Beyond the annotations declaring read-only, open-world, and idempotent behavior, the description adds meaningful context: signing secrets are never returned and are only shown once at creation. The hasMore explanation also clarifies list semantics beyond what annotations provide.

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?

The description is three sentences with no wasted words. It front-loads the core purpose, then adds the security disclosure and pagination guidance, with each sentence earning 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?

For a read-only list tool, the description is complete: it states scope, discloses a critical security behavior, and explains pagination semantics. An output schema exists to cover return-value details, so nothing essential is missing.

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?

The input schema already documents all six parameters with 100% coverage, so the baseline is 3. The description adds value by explaining when to pass nextPageToken and recommending filters over pagination, which gives additional semantic guidance for the pagination-related parameters.

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 a specific verb and resource: list the workspace's webhook endpoints, including their global event lists. The parenthetical '(webhooks group)' helps distinguish this tool from related webhook subscription tools in the sibling list.

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?

The description gives clear guidance on pagination behavior: hasMore means more items exist, narrowing filters is preferred over paginating, and nextPageToken should only be passed when every item is needed. It does not explicitly name an alternative sibling to use instead, but the context is clear enough for selection.

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