Get NEON data availability

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint. The description adds valuable behavioral context beyond these: it confirms no token is required and that the tool is a small GraphQL query, which affects cost and access assumptions. It also describes output modes and filtering, but the core safety profile is covered by annotations. This adds meaningful context without contradiction.

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 remarkably concise, with two sentences that front-load the core purpose and then add workflow guidance. Every phrase earns its place: it states what it returns, the modes, the optionality, the access requirement, and the next step. No filler or repetition exists.

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 complex tool with 12 parameters and an output schema, the description provides a clear high-level overview and a critical workflow pointer. It implies the parameter combinations (product/site, windowing, filtering, release/provisional) without exhaustively detailing them, but the schema covers the specifics. The output schema exists so return values are documented elsewhere. The only slight gap is explicit guidance on how to combine parameters for each mode, but overall it is sufficient for an agent to understand when and how to invoke it.

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?

Parameter schema coverage is high (83%), so most parameters are individually documented. The description adds some semantic context by describing the three modes (product/site/cell) and mentions 'month ranges per release including PROVISIONAL' and 'optionally windowed and filtered,' which maps to release, provisional, start_month, end_month, and filtering parameters. However, it doesn't deeply clarify the interplay of site_codes, domain_code, product_codes, or format beyond what the schema already explains, so the added value is marginal (baseline 3).

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 what the tool does: it returns data availability in three modes (product to sites, site to products, or a single product-site cell), including month ranges per release with provisional handling. This is a specific verb (get availability) and resource (NEON data), and it distinguishes itself from siblings by outlining distinct output structures, making it 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 a strong workflow hint: 'Next: call neon_list_files for a product, site and month range,' implying this tool is used for availability reconnaissance before listing files. It also notes that it works without a token and is small, which suggests it's a lightweight, preliminary query. However, it does not explicitly state when not to use it or explicitly contrast with siblings like neon_get_site or neon_search_products, so a 4 is appropriate.

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