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

The description describes an inherently read-only operation ('List all active webhook subscriptions', GET /v1/webhooks), but the annotations declare readOnlyHint=false and idempotentHint=false. This is a direct contradiction that would mislead an agent about the operation's safety profile. The cost-tier and endpoint metadata are useful, but the read/write mismatch dominates.

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?

One clear sentence front-loads the purpose, followed by compact structured metadata (group, endpoint, cost). Nothing is wasted, though the metadata tags are boilerplate rather than description prose.

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?

An output schema exists, so return values need not be explained, and the purpose is stated. But there is no usage context, no pagination/filtering note (only 'active' is implied), and the annotation contradiction leaves the agent's mental model incomplete.

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%, with both 'fields' (compact mode) and 'precision' fully documented in the schema, so the baseline is 3. The description adds no parameter detail of its own and never mentions the compact-mode projection controls, so it neither compensates nor detracts.

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 all active webhook subscriptions') plus the scope ('for the authenticated user'), so the agent knows exactly what it retrieves. However, it does not distinguish itself from the many sibling webhook tools (subscribe, id, id_test, event-specific triggers), so an agent can't rule out alternatives from the text alone.

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 when-to-use or when-not-to-use guidance and no named alternatives. The agent is left to infer that this is the read side of the webhook family from the verb 'List' alone.

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