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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond the raw endpoint path: no pagination, result scope, or authorization context for what 'for user' means.

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?

Two brief sentences with the purpose front-loaded before the endpoint. No filler, though the second sentence is largely redundant metadata for an agent.

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 zero-param read tool with no output schema, the definition is minimally viable: the agent knows what it fetches and that it is safe. The missing piece is disambiguation from the many sibling 'shared' webhook getters.

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 tool takes zero parameters, so there is nothing for the description to document; baseline 4 applies. The stated endpoint confirms the resource path but adds no parameter-adjacent meaning.

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?

States a clear verb and resource ('Get all shared webhooks for user'), but 'shared' is ambiguous about direction (shared by the user vs. shared with the user). Sibling tools get_webhook_bot_shared_by_id and get_webhook_bot_shared_with_id suggest that distinction matters, and this description does not resolve it.

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 when-to-use guidance and no mention of alternatives. The agent is not told how this differs from get_webhook_bot_shared_by_id, get_webhook_bot_shared_with_id, or get_webhook_data_shared, which all sound overlapping.

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