Create Webhook Subscription

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

Annotations declare write/open-world/non-idempotent, but the description adds real value beyond them: the returned signing_secret, the X-AstroWay-Signature HMAC-SHA256 verification scheme, and a 10-credit cost. It omits what happens if the URL is already registered or how to remove the subscription, so it stops just short of full behavioral coverage.

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 action and the key return concept, with compact bracketed metadata for group, endpoint, required fields and cost. Every sentence carries information, though the partial event list is arguably worse than none.

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?

Output schema exists, yet the description still usefully explains the signing_secret and signature header. For a two-parameter write tool with full annotations, the remaining gaps (duplicate/URL policy, lifecycle management) are secondary.

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 0%, so the description must carry parameter meaning — and it only partially does. It enumerates three event values ('report-ready, transit-alert, eclipse-alert') while the schema enum contains twelve, which risks misleading an agent about the valid set, and it says nothing about the url being a URI with a 2048-char limit.

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?

States a specific verb and resource ('Subscribe to outbound webhook deliveries'), which is clearly distinguishable from catalog/list siblings like astroway_webhooks_webhooks or astroway_webhooks_id. It never explicitly names which sibling to use instead, so sibling differentiation is implied rather than stated.

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?

The event list and 'POST /v1/webhooks/subscribe' endpoint imply when to call it, and the cost line gives a practical constraint. However, there is no explicit when-to-use guidance, no note on how to later inspect or delete a subscription (astroway_webhooks_webhooks / astroway_webhooks_id), and no statement about prerequisite auth or duplicate handling.

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