webhooks_get

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

Annotations already declare this as read-only, idempotent, non-destructive, and not open-world. The description adds useful behavioral context beyond annotations by stating that the secret is always masked and pointing to the correct alternative tool for obtaining a full secret.

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 two sentences, front-loaded with the core action and followed by the critical secret-masking caveat. Every sentence adds useful information with no repetition or filler.

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 get tool with full parameter schema coverage and annotations covering safety behavior, the description provides enough context to invoke it correctly. Since there is no output schema, it could say more about the returned configuration structure, but the secret-masking note covers the most important output caveat.

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 schema has 100% description coverage for both parameters, including uuid and companyId, so the structured data already carries parameter meaning. The description reinforces that this retrieves a single webhook endpoint via its UUID but does not add further syntax or format detail beyond the schema.

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 a specific verb and resource: retrieve the full configuration of a single webhook endpoint. It distinguishes this from related operations by naming webhooks_regenerate_secret and by emphasizing the single-endpoint scope, which contrasts with webhooks_list.

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?

It clearly explains the secret-masking behavior and routes secret retrieval to webhooks_regenerate_secret. It does not explicitly say to use webhooks_list for multiple endpoints, but the single-endpoint framing makes the distinction obvious enough.

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