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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Read' implies a non-mutating operation, and 'without its secret' discloses a key security-relevant behavior. However, it does not clarify what other fields are returned, whether any permissions or ownership checks apply, or what happens when the webhook does not exist. For a simple read operation this is adequate but not rich.

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?

The description is a single, immediately parsable sentence with zero filler. It states the verb, the resource, and the important exclusion ('without its secret') in that order, making the critical caveat front-loaded.

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 tool with only two required, well-described parameters and no output schema, the description is nearly complete: it tells the agent what operation is performed and the one notable behavioral caveat. 'Read a webhook' sufficiently implies the return value will be webhook data, and 'without its secret' prevents a critical misassumption. A full response-shape description would be a nice addition but is not essential for invoking the tool correctly.

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%, and both parameters already have clear descriptions: 'Webhook endpoint ID' and 'Active organization ID'. The tool description adds no additional parameter-level context, but none is needed because the schema already carries that burden.

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 uses a specific verb ('Read') and a specific resource ('a webhook'), and adds a meaningful qualifier ('without its secret') that helps distinguish this from listing or managing webhooks. An agent can immediately understand this is a single-webhook retrieval operation, especially given sibling names like webhooks and webhook_disable.

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?

The description implies when to use it — when you need a webhook's details excluding its secret — but it does not explicitly contrast with sibling tools like commsharbor_webhooks for listing or commsharbor_webhook_deliveries for delivery history. There is no when-not-to-use guidance, so an agent must infer routing from the tool name and context.

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