Register Return-Due Webhook

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

The description lacks critical behavioral details: the meaning of 'N days' is undefined, it does not specify whether the webhook replaces or overlaps with others, and the payload format or authentication needs are omitted. Annotations do not clarify these gaps.

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 extremely concise: one sentence for purpose, a group label, and an example. Every element is necessary and front-loaded, making it efficient for quick scanning.

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?

The description misses essential context: the value of 'N' is not defined, and there is no mention of what the webhook payload contains or if authentication is required. Given the simple schema, these omissions hinder full understanding.

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?

With 0% schema coverage, the description provides an example request body showing a URL, which adds context beyond the schema. However, it does not explicitly explain that 'url' is the callback endpoint, leaving some reliance on inference.

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 'Register Return-Due Webhook' clearly states the action and resource. The description 'Fires N days before a solar/lunar/planetary return is exact' specifies the event type, differentiating it from sibling webhook tools like webhooks_dasha_change or webhooks_eclipse_alert.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, when not to use it, or comparisons with similar webhook tools.

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