porkchop_plot_analysis

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

No annotations are provided, so the description carries full burden. It mentions error handling (errors returned as strings) and return format (JSON string), but lacks details on computational complexity, assumptions (e.g., two-body problem), or required ephemeris data.

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 concise and well-structured, using a clear docstring format with summary, args, returns, and raises. Every sentence serves a purpose, and the key information is front-loaded in the first sentence.

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 tool's complexity (5 parameters, date ranges, optional settings) and an existing output schema (not shown), the description covers the essentials: input descriptions, return type, and error handling. It could specify allowed celestial body names or date format constraints more precisely, 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?

Despite 0% schema description coverage, the description provides meaningful docstring-style explanations for each parameter (e.g., 'Departure celestial body name', 'Range of departure dates (ISO format)'). This adds significant value beyond the schema's bare types and titles. However, 'analysis_options' is described vaguely as 'Optional analysis settings'.

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 starts with a specific verb and resource: 'Generate porkchop plot for interplanetary transfer opportunities.' It clearly distinguishes from sibling tools like hohmann_transfer or lambert_problem_solver by focusing on delta-V contour plots for launch window identification.

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?

The description implies usage for analyzing interplanetary transfer opportunities via a date-grid approach, but does not explicitly state when to use this tool versus alternatives (e.g., hohmann_transfer for impulsive maneuvers). No when-not or alternative suggestions are provided.

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