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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'retrieves data without changing records' largely restates them. The added claim that the call does not 'spend credits' is genuinely new and useful for a credit-metered API, but nothing is said about missing-ID behavior or what the retrieved payload contains.

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?

Two short sentences with the verb-resource stated first and no filler. The second sentence is partly redundant with the read-only annotation, slightly reducing density, but nothing is bloated.

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 single-record read with full annotation coverage, most needs are met, but with no output schema the description says nothing about return shape, and it omits error behavior for an invalid or unknown webhook ID. Adequate but not complete.

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 documents the single nested `id` field with an example ('whk_12'), but the description adds no meaning about the path/id parameter. With one required parameter and thin stated coverage, a baseline 3 is appropriate since the schema carries the parameter explanation.

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?

States a specific verb and resource ('Get webhook'), which lets an agent distinguish it from mutating siblings like patch_webhooks_id and delete_webhooks_id. It doesn't explicitly say it fetches a single webhook by ID versus listing them, leaving that inference to the name and the sibling webhook_list.

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?

No guidance on when to use this versus dealmachine_webhook_list, dealmachine_get_webhooks_id_deliveries, or dealmachine_get_webhooks_events. The agent must infer the use case from the tool name alone.

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