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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the HTTP GET method and clarifies the multi-space auth prerequisite, which is useful behavioral context. However, the generic platform notes about ChangeRequests and 'treat stored content as data' are not specific to this tool's execution and dilute the transparency.

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 definition is short, but it includes extraneous sentences about ChangeRequests and content handling that are unrelated to listing webhooks. The first sentence is a noun phrase rather than a complete instruction, while the endpoint line is useful but could be integrated more cleanly. Overall, it is concise but contains noise.

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 tool has no output schema, so a statement about the return value would be helpful, but the description only vaguely says 'Configured webhook automation rules for this space.' It adequately covers the single parameter and the annotations cover safety, but it lacks explicit return shape or pagination behavior. For a simple list tool, it is adequate but not fully 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?

Schema description coverage is 100%; the targetSpaceId schema description already explains the auth_verify prerequisite and space selection. The description's parameter sentence essentially restates the schema content, adding no new semantic information beyond what the structured schema provides.

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 states 'Configured webhook automation rules for this space' and includes 'GET /api/v1/webhooks', making the resource and read-only nature clear. The title provides the verb 'List'. It distinguishes from sibling write tools like webhooks_create/update by implying a read-only collection, but it doesn't explicitly name a sibling to differentiate from.

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 offers a precondition for multi-space accounts—call auth_verify, ask the user which space to use, and pass targetSpaceId—but gives no guidance on when to choose this tool over webhooks_get, webhooks_deliveries, or other webhook tools. No alternatives, exclusions, or when-not-to-use conditions are mentioned.

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