webhooks_deliveries_get_to_many_related

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not pagination behavior, not whether the result set can be large, not auth requirements, not how filters interact. A raw HTTP path is not behavioral disclosure.

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 it wastes its only sentence by printing the identical path twice in parentheses. That is noise rather than information, and it is not front-loaded with anything an agent can act on.

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 an 8-parameter, no-annotation, no-output-schema tool, the description supplies no information at all. An agent must infer everything from the schema and the tool name alone, which is inadequate given the 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 100%, so all eight parameters (id, limit, include, fields_*, filters) are already documented in the schema, which sets the baseline at 3. The description adds nothing on top — no explanation of how the filter parameters combine or how include/fields affect the response.

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 is the endpoint path echoed back, duplicated verbatim in parentheses. It does imply the resource (deliveries for a given webhook id) via the URL, but it restates the tool name rather than stating a purpose in words, and it gives no basis for choosing between it and the near-identical sibling webhooks_deliveries_get_to_many_relationship.

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 guidance on when to use this tool, no mention of the sibling variant, no prerequisites, and no indication of what the caller should expect. Nothing in the description routes an agent between this and the many other webhook/delivery tools.

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