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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does not meet it. 'Map' implies a mutating association, but the description never states whether the operation is idempotent, what happens if the resource is already mapped to the webhook, whether duplicates are created or replaced, or what side effects occur. For a write-style tool with zero annotation coverage, this is a meaningful transparency gap.

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 two sentences with the core purpose front-loaded and a compact, bulleted 'Use when' clause. There is no filler or redundancy. It is slightly terse but every sentence earns its place, so a 4 rather than 5, which would demand a bit more useful substance packed in.

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?

The description covers purpose and usage trigger, the schema covers all parameters at 100%, and an output schema exists so return values need not be spelled out. The notable gap is behavioral depth (idempotency, duplicate handling, side effects), which was already penalized under behavioral transparency, leaving the definition adequate but not fully complete for a mutating tool.

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%, so the input schema already documents all four parameters (api_key, webhook_id, resource_id, resource_type) with meaningful descriptions. Per the rubric, high coverage earns a baseline of 3. The description's mention of resource types (job/monitor/monitor_group) mildly reinforces the resource_type parameter but adds no semantics beyond what the schema already provides.

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+resource ('Map a resource to a webhook') and enumerates the three accepted resource types (job, monitor, monitor_group), making the operation unambiguous. It implicitly distinguishes itself from create_webhook (creating the webhook itself) and remove_webhook_resource (the inverse unmapping), though it never names these siblings explicitly, which keeps it from a 5.

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?

A dedicated 'Use when' clause gives a clear trigger condition ('you want a webhook to fire for a specific job or monitor's deliveries'), which is solid usage context. However, it offers no exclusions and names no alternatives (e.g., remove_webhook_resource for unmapping, or trigger_webhook for manual firing), so it falls short of the explicit when-not/alternative guidance needed for a 5.

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