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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the description's burden is lower. It usefully discloses the shape of what comes back (URL, triggers, bound surveys), but adds nothing about error behavior for a missing id, permissions, or auth requirements.

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 tight sentences with the payload description front-loaded. The trailing 'Formbricks v2: GET /management/webhooks/{id}' is largely orientation detail that restates the path already implied by the id parameter, but it is brief and not harmful.

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 compensates by naming the returned fields, which is the main thing an agent needs. Nothing critical is missing for a simple single-resource read, though id sourcing and array/cardinality details for triggers and surveys are left unspecified.

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?

Only one parameter and schema coverage is 100%, so the schema fully documents webhook_id. The description adds no format, sourcing, or lookup hints (e.g. that the id comes from list_webhooks), leaving the baseline 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?

Names a specific verb (Fetch) and resource (a single webhook) and enumerates the payload it returns (URL, triggers, bound surveys). The singular 'a single webhook' implicitly separates it from the list_webhooks sibling, but that sibling is never named, so the differentiation is only inferred.

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?

Usage is implied by 'a single webhook' — the agent can infer this is the lookup-by-id tool rather than the enumerator. There is no explicit statement of when to reach for this versus formbricks_list_webhooks, nor any prerequisite (e.g. needing an id obtained from the list call).

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