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

Annotations already declare not read-only, not idempotent, not destructive, and closed-world. The description goes beyond them by enumerating non-effects (no autonomous daemon, no publication, no LLM call, no persistent game) and the call-budget bound, which genuinely informs the agent about side-effect scope.

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?

Front-loaded with the action, then the precondition, input constraint, return shape, and negative guarantees. Each sentence earns its place with no filler.

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?

An output schema exists, so return values need not be spelled out, and the description still notes the key outputs. Combined with the precondition and input format, it is nearly complete, though the 'agreed call budget' concept is asserted without saying how it is determined.

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 0% for the single parameter, so the description must compensate; it does, specifying that journal_json is complete closed JSON rather than GardenScript and capped at 64 KiB. That tells the agent the accepted format and a failure mode the bare schema does not.

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 (Execute) and resource (one bounded whole-farm Rust journal), with a scope qualifier ('bounded'). An agent can distinguish it from farm_workshop_get (read) and validate_gardenscript, though siblings like farm_policy_run are not explicitly contrasted.

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?

Gives a clear precondition: run only 'after human agreement, within the agreed call budget,' which distinguishes it from read-only siblings. It stops short of naming which alternative to use when agreement is absent or the budget is exhausted.

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