venus_star_points_conjunctions

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

Discloses credit cost and return fields beyond annotations (readOnlyHint). No contradictions; description adds transparency about output contents and cost.

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?

Concise: two short sentences plus an example. Front-loaded purpose, then returns, then cost. No redundant text.

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?

For a simple query tool with no output schema, description covers purpose, inputs (via schema), and return contents. Lacks mention of any prerequisites but is largely complete.

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% with descriptions for all three parameters. Description uses start_date/end_date in example but adds no semantic meaning beyond the schema. Baseline 3 for high coverage.

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?

Description clearly states 'Find all Sun-Venus conjunctions in a date range' with specific verb and resource. Lists return fields, distinguishing from sibling tools like 'venus_star_points' and 'venus_phase'.

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?

Implies usage for finding conjunctions within a date range and provides an example, but does not explicitly state when to use vs alternatives like 'venus_star_points' or 'venus_phase'. No exclusions or when-not guidance.

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