linear_getWebhookById

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

The description adds minimal behavioral context beyond the annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true) with the phrase 'ordinary workspace webhook'. While annotations already convey the safe read nature, the description does not provide additional details about response format, rate limits, or access requirements.

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 sentence that conveys the core functionality without extraneous words. It is appropriately front-loaded and concise, though it could be slightly expanded for clarity without losing brevity.

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 (get by ID) and the presence of an output schema, the description is complete enough for an agent to understand its purpose. However, it could benefit from clarifying what 'ordinary workspace webhook' means in contrast to other webhook types.

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 description mentions 'by ID' but does not explain what the 'id' parameter represents or how to obtain it. With 0% schema description coverage, the description should provide more context about the parameter's meaning, but it falls short.

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 clearly states the verb 'Get', the resource 'one ordinary workspace webhook', and the method 'by ID'. This distinguishes it from siblings like linear_getWebhooks (for listing all webhooks) and other webhook mutation tools.

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 that the tool is for retrieving a specific webhook when you have its ID, but it does not explicitly state when to use this tool versus alternatives like linear_getWebhooks for listing or linear_getManagedOAuthApplicationById for other resources.

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