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

Annotations already declare readOnlyHint=false and destructiveHint=false, so safety is covered. The description adds the useful, non-annotated fact that the tool supports a confirm/dry-run preview and idempotency validation, but says nothing about the permission requirements, what the created task returns, or what happens on duplicate submissions. Note the mild tension with idempotentHint=false, which the client-supplied idempotencyKey only conditionally overrides.

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 short sentences with the action front-loaded and no filler. It is efficient, though its brevity contributes to the missing context noted elsewhere rather than being a model of dense concision.

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?

With eight parameters, no output schema, and annotations that only cover the safety profile, the description does the minimum: it names the resource and two behavioral flags. It omits prerequisites (e.g. that farmId must reference an existing farm) and what a successful creation yields, leaving the agent to infer those.

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 description coverage is 100%, so the baseline is 3 regardless. The description merely echoes the confirm and idempotencyKey parameters already documented in the schema and adds no syntax, defaults, or interaction details beyond them.

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?

States a specific verb and resource ('Create a new farm management task'), which is enough to tell it apart from sibling creation tools like create_hive or create_calendar_event by resource. It stops short of naming any sibling or scope constraint explicitly.

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?

'Supports confirm and idempotency validation' hints at a dry-run workflow but gives no when-to-use guidance, no prerequisites, and no routing to alternatives. Nothing tells the agent when this tool is the right choice over the many other create_* siblings.

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