Api webhooks endpoints retrieve

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by noting that unauthorized related fields are masked, though it does not describe permissions or the response shape.

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?

It is a single concise sentence with no filler and leads with the return action. However, it is under-specified and could use the space to name the resource being retrieved.

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 retrieve endpoint, the annotations cover safety and idempotency, and the description adds the masking behavior. It is minimum viable, but still omits the target resource, id semantics, and what unauthorized masking means in practice.

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?

The schema has one required id parameter with 0% description coverage, and the description never mentions the id or explains what kind of identifier it expects. It only implies a single-object lookup, so it does not compensate for the schema 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 says "Return a single object," which restates the retrieve action but never identifies the resource as a webhook endpoint. It does not distinguish this tool from sibling retrieve/object_retrieve endpoints.

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 guidance about when to use this tool versus the webhooks endpoints list or object_retrieve alternatives. The only implied usage is retrieving one item, but no selection criteria are given.

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