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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: the result is a fixed catalog of exactly 22 events, and full payload detail requires a follow-up fetch call. It does not discuss result size or ordering, but with zero parameters neither is a real risk.

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 sentences, front-loaded with the invocation trigger and followed by the return contract and the escalation path. The middle clause enumerating example questions is slightly verbose but earns its place by covering the range of phrasings a user might use.

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 zero-parameter, read-only catalog tool with no output schema, the description covers everything an agent needs: when to call it, that it returns all 22 events with payload fields, and which sibling tool to use for full detail. 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 tool takes no parameters, so the baseline is 4 and there is nothing for the description to compensate for. Nothing in the description misleads about inputs, and it correctly frames the tool as argument-free.

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 (returns the complete catalog of all 22 Branch webhook events with payload fields), which is concrete enough for an agent to know exactly what comes back. It also implicitly separates itself from the sibling 'fetch' tool, which is named as the way to get per-event detail.

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?

Opens with an explicit trigger condition ('Call this when the user asks about Branch webhooks, events, notifications, or callbacks') and enumerates the sub-cases it covers — which events exist, what data an event contains, which event fires during onboarding or payment. It then names the alternative (fetch with a listed doc id) and the condition that selects it.

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