Stream Lunar Phase

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

Annotations provide readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, but the description adds minimal behavioral insight. It does not clarify whether the tool provides a one-time snapshot or a continuous stream, nor does it explain any side effects or authentication needs. The example body '{}' contradicts the schema's required 'body' field, causing confusion.

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?

The description is extremely concise, consisting of two short sentences plus a group label and example. Every element serves a purpose without redundancy.

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?

Given the absence of an output schema, the description should elaborate on the return format, update frequency, or other behavioral details for a real-time streaming tool. It only mentions 'Current 8-phase + countdown to next major phase', which is insufficient for an agent to fully understand the tool's output.

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?

The schema defines a single required 'body' parameter as a freeform JSON object, with a vague description referencing the tool description. The tool description only provides an empty example body, which conflicts with the required constraint. No parameter details (e.g., allowed fields, format) are given, leaving the agent to guess.

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 description states the tool provides 'Current 8-phase + countdown to next major phase' which clearly indicates lunar phase information. The '[Group: Real-time Streaming]' label adds context, but it does not distinguish from sibling tools like moon_phase or lunar_calendar, which may serve similar purposes.

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 guidance is provided on when to use this tool versus alternatives. The description lacks any context about prerequisites, intended use cases, or exclusions, leaving the agent to infer from the name alone.

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