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

Annotations already declare the safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false), and the description adds genuinely useful context: the event that triggers firing and a cost of 10 credits (Tier 1). It does not explain what happens on duplicate registration, retries, or failure handling, which matters for a non-idempotent write.

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 compact and front-loaded: the trigger event leads, followed by bracketed metadata tags for group, endpoint, required param, and cost. Every element carries information with no filler.

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 the safety profile. However, for a webhook-registration tool sitting among a dozen similar siblings, the absence of any disambiguation or registration-semantics detail leaves a real gap.

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 67%: fields and precision are self-documented in the schema, while url has no schema description and is only echoed as '[Required: url]'. The description adds no syntax or format detail beyond what the schema already provides, so the baseline 3 is appropriate.

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 first line states the trigger event ('Vedic Vimshottari dasha period transitions') and the endpoint (POST /v1/webhooks/dasha-change) plus title make the action (registering a webhook) clear. It does not explicitly differentiate from the many sibling webhook tools (e.g. mahadasha_end), but the resource and event are specific enough to identify the tool.

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 when-to-use guidance, no prerequisites, and no routing among the ~13 sibling webhook tools. An agent cannot tell from the description when dasha_change should be preferred over mahadasha_end or retrograde_start.

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