get_webhook

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered and the bar is lower. The description's only added behavior is the omit-defaults-to-project-level rule, which is really parameter semantics; it says nothing about the return shape or behavior when no webhook is configured.

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, zero filler, with the core action front-loaded and the parameter branching immediately after. Every sentence 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?

For a parameterless-required read tool with full schema coverage and annotations covering safety, the description is nearly complete. The main gap is that no output schema exists, yet the description doesn't hint at what the returned configuration contains.

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% for the single optional parameter, so the schema carries the burden and the baseline is 3. The description's phrasing about agent_id closely mirrors the schema's own text, adding little new meaning.

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 (Get) and resource (webhook configuration), and clarifies the two retrieval scopes: agent-specific vs project-level default. It does not explicitly contrast with siblings like set_webhook or list_webhook_deliveries, so it falls short of full sibling differentiation.

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?

Gives clear situational guidance for the branch: pass agent_id for an agent-specific webhook, omit it for the project-level default. It stops short of naming alternatives or exclusions (e.g., when to use set_webhook or list_webhook_deliveries instead).

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