usda_ag_query

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

Annotations already indicate readOnlyHint=true. The description adds the 50,000 record limit behavior beyond annotations, which is useful. However, it does not detail any other behavioral traits like performance or required permissions.

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?

Two concise sentences with no filler. The first sentence states purpose, the second provides limits and usage guidance. Ideal structure.

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 exists, but the description doesn't explain return format. However, it covers the important aspects: custom query, limits, and when to use sibling. For a query tool, it is fairly complete given context signals.

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?

Input schema has 8 parameters all with descriptions, achieving 100% coverage. The description's statement 'any combination of filters' implies all parameters are optional, which is a minor addition. Baseline 3 is appropriate as the schema handles most parameter meaning.

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 it is a custom query tool for USDA NASS QuickStats with any combination of filters. It specifies the resource (USDA NASS QuickStats) and action (query), and distinguishes from sibling tools like usda_crop_data and usda_livestock which are more specific.

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?

Explicitly mentions a maximum record limit of 50,000 and advises using usda_ag_count first for large queries, providing clear when-to-use and when-not-to-use guidance.

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