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

Annotations supply a safety profile (readOnlyHint=false, idempotentHint=false, openWorldHint=true), but they are puzzling for an alerting tool and the description does nothing to resolve that. The "[Group: Real-time Streaming]" and 10-credit cost tags are useful metadata, yet the description never explains what streaming means here, whether it blocks, or how alerts are delivered.

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 functional sentence comes first, followed by two bracketed metadata tags that each carry real information (grouping and cost). Nothing is padded, though the terseness borders on under-specification.

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 prose, but for a paid (10 credits), streaming, alert-oriented tool sitting among many near-identical stream/webhook siblings, the definition omits the usage and behavior context an agent needs to select it correctly.

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 100%, so `fields` (dotted-path compaction) and `precision` (decimal rounding) are already fully documented with examples in the schema. The description adds no parameter information, so the baseline 3 applies.

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?

"All planets retro state + next stations" names a concrete resource (planetary retrograde/direct stations) with a specific scope (all planets), which is distinguishable from siblings like astroway_stream_void_of_course and astroway_stream_ingress. It is verb-less and telegraphic, but the subject matter is unambiguous.

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 indication of when to call this versus the closely related astroway_webhooks_retrograde_start/end or astroway_stream_transit_alerts. Whether this is a one-shot snapshot of current retrograde state or an actual continuous stream is never clarified, which is exactly the decision an agent needs to make.

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