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

Annotations declare it is a non-read-only, open-world, non-idempotent mutation, so the safety profile is covered. The description usefully adds the cost (10 credits, Tier 1) and the default timing, which are not in structured fields, but says nothing about auth requirements, delivery semantics, or what happens on re-subscription.

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-loads the core action in one sentence, then uses bracketed metadata for group, endpoint, requirement, and cost. Efficient and scannable 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?

With an output schema present, return values need not be explained, and the description covers endpoint, required param, cost, and default behavior. The main omission is usage routing against the streaming eclipse siblings, which is a guidance gap rather than a completeness one.

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 well documented in the schema, while `url` has no schema description. The description only echoes '[Required: url]' and adds no syntax or format detail beyond the schema, so 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?

States a specific verb ('Subscribe') and resource ('upcoming eclipse alerts') with the default lead time (7 days before). Combined with the [Group: Webhooks] tag, an agent can place it against streaming siblings, though it never explicitly contrasts itself with astroway_stream_eclipse_incoming.

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 or when-not-to-use guidance and no named alternatives. The 'default 7 days before' hints at behavior but the description never tells the agent when a webhook subscription is preferable to the eclipse streaming tools.

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