Fruit Picking Farms

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is clear. The description adds that month filtering automatically narrows results to fruits in season, and that it returns booking links and map coordinates, which are useful behavioral details 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?

Two sentences structure: first sentence states when to use and what is returned, second sentence provides an important condition for sibling tool usage. No unnecessary words or repetition. Front-loaded with essential 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 simplicity of the tool (4 optional parameters, no output schema), the description covers the main points: what it returns (farms, booking links, map coordinates), the month filtering behavior, and the sibling tool usage. Could be slightly more specific about the output structure, but adequate for the complexity.

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?

Schema coverage is 100%, with each parameter having a descriptive title and description. The tool description does not add new meaning to the parameters beyond what the schema already provides, so it does not improve 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?

Clearly states that the tool returns fruit-picking farms, booking links, and map coordinates. Differentiates from the sibling tool 'fruit_seasons' by specifying that if the user only asks which fruit is in season, that tool should be called first.

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 tells when to use this tool: when the user needs actual fruit-picking farms. Also provides a clear when-not condition: if the user only asks which fruit is in season, call 'fruit_seasons' first. This directly addresses the most likely alternative.

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