Get webhooks

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds a concrete operational constraint the annotations do not carry: 100 requests / 10 seconds per shop, plus a link to the rate-limiting guide. That is genuine added behavioral context, though pagination or result-size behavior is still unstated.

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?

It is short, but the ordering is poor: a rate-limit warning leads while the actual purpose ("Get webhooks") trails and merely echoes the title. Every word is technically in bounds, yet the front-loaded content is the least important part.

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 list endpoint with no output schema, the description should at minimum signal what is returned (collection of webhook records) and whether results are paginated. It covers the rate-limit dimension well but leaves the core list semantics implicit.

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% and the single 'account' parameter is well documented in the schema itself as an exact private shop profile label. The description adds nothing about the parameter, so the baseline 3 applies.

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 name and the phrase "Get webhooks" identify the resource, but the description is essentially a restatement of the title rather than a statement of what the tool returns. It never clarifies whether this is a paginated listing of all shop webhooks versus a single lookup, even though the sibling get_webhook makes that distinction critical.

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?

There is no when-to-use guidance at all. With siblings get_webhook, create_webhook, update_webhook and delete_webhook present, the description should say this is the enumeration counterpart to get_webhook, but it offers nothing.

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