Planting window

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

The description clearly discloses the data source ('ten years of observed daily minima') and honestly states that 'no source this server reads publishes those, so they are never guessed' regarding days_to_maturity and frost_tolerance. It also explains that hardiness_zone alone cannot provide frost dates fires. The annotations (readOnlyHint, openWorldHint) are consistent. The description adds substantial behavioral context beyond the 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?

The description is a single, dense sentence that efficiently conveys the purpose, data source, and optional parameters. Nofluff, no repetition, and structured logically from core function to optional enhancements.

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?

The description covers the main inputs and outputs, data source, and limitations (no guessing of maturity/tolerance). It doesn't specify output format, but that's not strictly necessary. It also doesn't mention error cases, but the schema covers bounds. Overall, it's informative and sufficient for an agent to decide and use the tool.

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?

All 7 parameters have schema descriptions, with 100% coverage. The tool description adds context by explaining the role of days_to_maturity and frost_tolerance (user-supplied) and the advisory note that they are never guessed. It also clarifies that hardiness_zone is only used when coordinates are unavailable. This goes beyond the schema, enhancing parameter understanding.

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+resource: 'Frost envelope and hardiness for a location.' It clearly states what the tool derives: last spring frost, first autumn frost, season length, and USDA zone from coordinates. It also differentiates from sibling tools (search_plants, plant_details, companion_check) by focusing on climatic data for planting, making its purpose 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?

The description gives explicit guidance on when to supply `days_to_maturity` and `frost_tolerance` to obtain transplant and sow-by dates, and notes that these are not sourced from the server. It implies that coordinates are preferred, and that hardiness_zone is only a fallback. It does not explicitly contrast with sibling tools, but the tool's specific inputs (coordinates, plant) and outputs (frost dates, zone) make usage clear.

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