get_farm

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

With no annotations, the description carries the transparency burden. 'Get details' sufficiently signals a read-only retrieval operation, but it does not describe error behavior (e.g., not-found), response shape, or any permissions required, leaving some behavior implied rather than explicit.

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?

One short, front-loaded sentence with no filler. It states exactly what the tool does and is easy to scan.

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 simple one-parameter retrieval with a fully documented schema, the description plus schema provides enough to invoke the tool correctly. It lacks detail about return contents and error cases, but complexity is low and no output schema exists, so this is a minor gap.

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 schema already documents farm_id with 100% coverage, so the baseline is 3. The description adds no new information about the parameter beyond 'specific farm,' which loosely references the ID but doesn't explain format, constraints, or source.

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 states a clear verb ('Get') and resource ('a specific farm'), indicating this tool retrieves one farm rather than listing or modifying. It is slightly generic and doesn't differentiate from sibling get_* tools, but the 'specific farm' phrasing clearly distinguishes it from list_my_farms.

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 phrase 'a specific farm' implies this tool is for retrieving a single farm when its ID is known, but the description does not explicitly mention when not to use it or point to alternatives such as list_my_farms for listing multiple farms.

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