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

Annotations already indicate readOnlyHint=true, so the operation is read-only. The description adds valuable context beyond annotations: 'secret material never included', which warns the agent that sensitive fields will be absent. This is useful behavioral information not captured in structured annotations.

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, focused sentence that front-loads the core action and immediately adds the security caveat. No filler words; every part earns its place.

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?

Given the tool's simplicity (one parameter, no output schema) and the readOnly annotation, the description is nearly complete. It explains what it does and a key behavior (secret redaction). No output schema exists, but the return is implied to be the endpoint object. For a read-only fetch, this is adequate.

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 0% because the description does not elaborate on the 'id' parameter. However, the description mentions 'by id', which reaffirms the parameter's role. Since the parameter is self-explanatory (an id), the description adds minimal additional meaning, but the 'id' mention is slightly helpful.

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 and resource: 'Get one webhook endpoint by id'. It clearly differentiates from siblings like webhookEndpoints_list (which retrieves multiple) and create/delete/update operations. The phrase 'one' and 'by id' makes the scope explicit.

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 usage when you have a known id, and the sibling set makes alternatives obvious (list for multiple, create/update/delete for modifications). However, there is no explicit statement of when to use this tool versus alternatives, nor exclusions or conditions that might warrant using another tool.

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