Register Mahadasha-End Webhook

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

Annotations are minimal (openWorldHint=true). Description does not clarify what 'N' is (not a parameter), whether registration updates existing webhooks, or side effects. Adds only the trigger event context.

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?

Extremely concise, front-loaded with key info. Group label helps categorization. Every sentence adds value without waste.

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?

Tool is simple with one parameter and no output schema. Missing details: what is N? Is it configurable? No info on response or errors. Adequate but has gaps.

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?

Only parameter 'url' has no schema description. Description only gives an example URL, not explaining its purpose or constraints beyond what the schema already indicates (type, format). Does not compensate for low schema coverage (0%).

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?

Clearly states it fires N days before a Vimshottari mahadasha ends. Differentiates from sibling webhook tools by specifying the trigger event (mahadasha end). Verb 'fires' and resource 'webhook' are explicit.

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?

Provides an example request body but no guidance on when to use this vs other webhook tools (e.g., webhooks_dasha_change, webhooks_transit_trigger). No when-not or alternative conditions mentioned.

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