Register Mahadasha-End Webhook

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

Adds real value beyond the annotations: the endpoint path, the required field, and a concrete cost (10 credits, Tier 1). However it does not explain the non-idempotent behavior declared in annotations (what happens if the same URL is registered twice), how to unregister, or what payload the URL will receive.

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?

Front-loaded with the event condition, followed by a compact bracketed metadata block covering group, endpoint, required field, and cost. Efficient overall, though the bracketed tags read like raw API metadata rather than explanatory prose.

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?

An output schema exists, so return values need no explanation, and annotations cover safety semantics. Still, key operational facts are missing for a webhook-registration tool: how the 'N days' lead time is set (no parameter exists), whether a chart/profile must already exist, and how subscriptions are listed or removed via astroway_webhooks_id.

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 coverage is 0%, so the description must carry parameter meaning, but it only repeats '[Required: url]', which the schema's required array already states. It says nothing about the URL being a publicly reachable HTTPS endpoint, verification handshakes, or how the unspecified 'N days' lead time is configured (no such parameter exists in 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 names the precise triggering condition (N days before a Vimshottari mahadasha ends), which clearly separates it from the dasha computation siblings and from unrelated webhook events. It never states the actual action verb (register/subscribe a webhook), so the agent must infer that from the title and the [Group: Webhooks] tag.

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 choose this webhook versus astroway_webhooks_dasha_change (which presumably also covers mahadasha transitions) or astroway_webhooks_subscribe. The trigger timing hints at its use case, but no exclusions, prerequisites, or alternatives are stated.

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