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

The readOnlyHint annotation already declares this as a safe read operation, so the bar is lower. The description adds genuine value beyond annotations with 'secret material never included', disclosing that the response deliberately omits secrets — useful for the agent to know it cannot extract secret values from this endpoint. No contradiction with annotations exists.

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?

A single 10-word sentence that front-loads the action and scope, with a parenthetical caveat appended. Every word earns its place; there is no fluff, repetition of the tool name, or boilerplate.

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 get-by-id read tool with safety annotations and no output schema, the description is largely complete: it states scope and a key response characteristic (no secrets). Minor gaps remain — no mention of not-found/error behavior or the general return shape — but these are low-risk for this operation and partially mitigated by the readOnlyHint.

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 coverage is 75%, with id lacking any semantic description (only minLength: 1). The description compensates by clarifying that id is the lookup key for the specific endpoint to fetch. The other three parameters (context, llm_model, conversation_id) are already well-documented in the schema, so the description's marginal addition to id meaningfully closes the gap.

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 ('Get'), a resource ('webhook endpoint'), and a precise scope ('one by id'), which clearly distinguishes it from siblings like webhookEndpoints_list (fetch all) and webhookEndpoints_deliveries_list. The parenthetical about secret material adds a meaningful qualifier without obscuring the core action.

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 the phrase 'by id' — the agent can infer this tool is for fetching a single endpoint when an id is known. However, the description never explicitly names alternatives or when-not-to-use conditions, such as 'to fetch all endpoints use webhookEndpoints_list' or 'for updating use webhookEndpoints_update'. The guidance is adequate but left to inference.

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