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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: the returned payload shape (events and target URLs) and the explicit security guarantee that authentication keys and tokens are never returned — an important disclosure for an agent deciding whether this tool can answer a credential-related question.

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 plus an endpoint path, front-loaded with the payload description before the security note. No wasted phrasing; the only marginal element is the raw endpoint path, which is mildly useful context rather than noise.

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, the description does the necessary work of saying which fields come back and what is withheld, and the three optional parameters are fully covered by the schema. Pagination semantics are handled in the schema's items_per_page note, so nothing an agent needs to call this correctly 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?

Schema description coverage is 100%, so page, fiscal_id and items_per_page are already documented including defaults and the max of 30. The description adds nothing on parameters beyond implying account scoping, which makes the schema baseline of 3 appropriate.

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 the specific resource (webhooks) and enumerates what is returned: events and target URLs, scoped to the account. It lacks an explicit verb like 'List', but the resource and scope are unambiguous and no sibling tool overlaps (no other webhook-related tool exists).

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?

There is no statement of when to call this versus alternatives, no prerequisite or permission context, and no guidance on iterating pages even though the tool is paginated. Usage is only inferable from the read-only listing nature of the tool.

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