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

There are no annotations, so the description carries the full burden. It discloses pricing per endpoint ($0.05–$0.15), data sources (USDA + ERS), and coverage (Global), which are useful operational details. However, it does not mention whether authentication is required, rate limits, error behavior, or whether the tool modifies any state; the informational nature is implied by terms like 'finder' and 'guide' but not explicitly stated.

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 opens with a clear one-sentence summary and then uses a structured bullet list of endpoints with prices, which is easy to scan. However, the endpoint list is quite long (15 items) and could potentially be condensed, but given the tool's multiple actions, the detail is justified and every line carries factual information.

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 (15 actions, 24 parameters, no output schema), the description is incomplete. It fails to map specific parameters to their relevant actions, leaving the agent to infer parameter usage through the schema. It also does not describe the structure or content of responses, which is critical since there is no output schema.

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?

The input schema covers 100% of the 24 parameters with descriptions, so a baseline of 3 is appropriate. The tool description does not add any parameter-specific meaning; it only lists endpoint names and prices, which are not directly tied to parameters. The schema itself provides all relevant parameter explanations.

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 identifies HarvestPulse as a global farm-to-table and agricultural intelligence API, and enumerates 15 distinct endpoints with one-line descriptions (e.g., 'find: Local Farm & Market Finder', 'season: Seasonal Produce Calendar'). This gives a specific verb+resource for each capability and distinguishes the tool from unrelated sibling pulse APIs.

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 provides strong context about the tool's domain and coverage ('Global', 'USDA + ERS data synthesis'), implying when it should be used for agricultural/food-related queries. However, it does not explicitly mention alternative tools or boundary conditions, such as when not to use HarvestPulse or which sibling tools to use instead.

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