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

With no annotations provided, the description must carry the full behavioral burden. It says 'Record' and mentions 'fare,' hinting at billing, but it does not disclose that the operation persists writes, requires an npub for credit billing, supports amendment via item_id, or that retire_ids only retires items without deleting them. These side effects are left to the schema.

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 is two short sentences with the action front-loaded and the rationale second. It avoids restating parameter names or schema content, and the 'afternoon in the field' rationale earns its place by explaining the batch-call design.

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?

The tool has 7 parameters, no annotations, and an output schema signal, so the description alone is not fully self-sufficient. The schema fills in most parameter-level details, but the definition still lacks explicit behavioral framing for a mutating, billing-related write tool. It is adequate if the agent reads the schema carefully, but not complete on its own.

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 86%, so most parameters are already documented. The description's 'what you grow, watch for, or saw' adds a light conceptual mapping to the kind values, but it does not clarify item shapes, the npub requirement, season defaults, or retire semantics beyond what the schema provides. This matches the baseline for high schema coverage.

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 opening clause 'Record what you grow, watch for, or saw on a plot' is a specific verb-plus-resource statement and maps well to the tool's planting/pest/wildlife/observation item kinds. The batch framing makes the write intent clear, though it does not explicitly distinguish itself from siblings such as goodearth_block_item_list or goodearth_block_save.

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 second sentence gives a clear context: use one call for many field notes rather than a separate fare per note. However, it does not explicitly name alternatives or state when not to use the tool, so the usage guidance is implied rather than fully articulated.

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