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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds one genuinely useful piece of behavioral context — that only metadata/approved fields are returned and secrets, contacts and original files are excluded — but says nothing about result shape, ordering, or what 'authorised' gates.

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 with the scope constraint front-loaded ahead of the exclusion list. The phrase 'through the existing application' is the only wasted clause.

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 simple, non-destructive list tool with a fully covered safety profile and no output schema, the definition is minimally sufficient. However, it omits what the returned metadata contains and how the paging/filter parameters behave, which matters for correct invocation.

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% and the description never mentions limit, query or offset. With three undocumented optional parameters, the description fails to compensate for the schema gap, leaving the agent to guess what 'query' matches against and how paging works.

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 ('Read') and resource ('webhook metadata') and narrows the scope to 'authorised' metadata. It is unambiguous about what is being listed, though the phrase 'through the existing application' adds noise rather than differentiation, and no sibling is named.

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 guidance on when to call this versus alternatives, nor any mention of the pagination/filtering model even though the tool exposes limit/offset/query. The only usage-adjacent signal is 'authorised', which implies a permission prerequisite but doesn't explain it.

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