wrike_get_webhook

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

No annotations are provided, so the description carries the full burden. 'Get' implies a read-only operation with no side effects, but the description does not explicitly state this or provide context on permissions, error handling, or response behavior. It is minimally adequate but lacks depth beyond the verb.

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, front-loaded sentence with no wasted words. It communicates exactly what the tool does without redundancy.

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 (one parameter, no output schema, no annotations), the description is complete enough for an agent to invoke it correctly. The parameter is fully documented, and the behavior is straightforward. Some might argue it could say what is returned, but for a simple get-by-ID, this is sufficient.

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% with webhookId fully documented as 'Webhook ID (required)'. The description's 'by ID' adds no additional meaning beyond the schema. With high coverage, the baseline of 3 applies.

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 uses the specific verb 'Get' with the resource 'webhook' and scoping 'by ID', clearly distinguishing it from sibling tools like wrike_list_webhooks (list all), wrike_create_webhook (create), wrike_update_webhook (update), and wrike_delete_webhook (delete). No ambiguity exists.

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 usage when a specific webhook ID is known and its details are needed. However, it does not explicitly contrast with alternatives like wrike_list_webhooks, nor does it state exclusions or prerequisites. Guidance is implied rather than explicit.

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