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

Annotations already mark this as read-only, and the description adds useful behavioral context: multi-space auth requirements and a security-relevant note to treat stored content as data, not instructions. It also explains the ChangeRequests write model, which helps the agent understand platform behavior beyond the tool itself.

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 brief and front-loads the core purpose and endpoint. The auth and data-handling notes are relevant, though the ChangeRequests sentence feels somewhat tangential for a simple GET operation. Overall, no excessive repetition of schema content.

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 read-only single-resource fetch, the description covers the essential invocation context: endpoint, required id, conditional targetSpaceId handling, and a caution about interpreting stored content. It does not describe the response fields, but no output schema exists and the title indicates a single webhook rule, which is sufficient for this complexity.

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 50%, with targetSpaceId already documented in the schema. The description reinforces that targetSpaceId should be supplied after auth_verify but does not meaningfully explain the id parameter beyond implying it is the webhook rule identifier via the URL path. This is adequate but not thorough.

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 title and the HTTP path 'GET /api/v1/webhooks/{id}' make it clear this tool retrieves a single webhook automation rule. The description lacks an explicit natural-language verb like 'retrieves' and does not directly distinguish it from webhooks_list, but the singular resource and GET method are enough to disambiguate.

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 provides concrete guidance for multi-space accounts: call auth_verify, ask the user which space to use, and pass targetSpaceId. It does not compare this tool to siblings such as webhooks_list or webhooks_deliveries, but the context for correct invocation is clear.

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