electional_station_tracker

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

Annotations indicate readOnlyHint=true, and the description confirms it's a read operation. Adds value with credit cost (3 credits per call) and smart defaults, providing context beyond annotations.

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?

Description is well-structured with sections, examples, and bullet points. Could be slightly more concise, but effectively communicates key information without waste.

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?

No output schema, but description includes 'Returns exact station times, longitudes, and signs.' Covers main parameters and defaults. Minor gaps like pagination or limits, but sufficient for the tool's complexity.

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 100%, so baseline is 3. Description adds examples of usage and default planet lists (e.g., 'Mercury through Saturn'), enhancing understanding beyond the schema descriptions.

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 clearly states the tool finds 'all upcoming retrograde and direct stations for planets in a date range.' It specifies the verb (find), resource (stations), and scope (upcoming, date range), effectively distinguishing it from siblings like ephemeris_retrograde_status.

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?

Provides explicit example queries: 'When does Mercury go retrograde?', 'Is Venus retrograde this year?', etc. and a 'USE THIS TOOL FOR' section. Lacks explicit exclusion of alternatives, but the examples and purpose are clear enough.

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