clio_list_webhooks

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful context about the `effect` parameter being required and verified as 'read' by Spring, and about the restricted routing authority. It does not describe return values or pagination, but the output schema reduces the need for that.

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 compact and well-structured: an identity line, a one-sentence routing constraint, and a bulleted argument list. It front-loads the tool name and avoids unnecessary prose. The arg list is justified given the lack of schema descriptions, so each line 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?

The presence of an output schema and safety annotations reduces the need for return-value and risk explanations. The description sufficiently covers routing and parameter semantics for a generic connector wrapper. Yet it lacks webhook-specific context (e.g., what filters or fields the connector expects) and does not clarify which parameters are relevant for a read operation versus write resumption, making it somewhat generic.

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 0%, so the description must compensate. It provides brief but meaningful semantics for all 7 parameters: e.g., project_id is 'Authenticated Project UUID', connector_account_ref is 'Project-bound connector account alias', and effect is 'Required and must be read; Spring verifies it.' This goes beyond the bare schema titles. However, it does not explain the expected structure of the `arguments` JSON, leaving some ambiguity.

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 identifies the operation as a Clio connector operation to list webhooks, with the platform tool name `clio.list_webhooks`. The verb and resource are unambiguous, and the 'Clio' prefix differentiates it from sibling list_webhooks tools of other systems. However, it does not explicitly elaborate on what a webhook is or what the list contains.

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 is given on when to use this tool versus alternatives such as clio_get_webhook or clio_create_webhook. The only constraint, 'Routes only through the exact project/account governed connector authority,' is a routing precondition, not a selection criterion. There is no mention of exclusions, alternatives, or conditions that favor this tool.

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