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

With no annotations, the description carries the full burden and does add value by explaining the as_of historical snapshot semantics and that sorting/searching operate over the entire block, not just the current page. However, it does not explicitly note the operation is read-only, nor cover auth/billing aspects (npub, dpop_token), leaving those 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 compact—three sentences with no redundant content. The first sentence is a memorable summary, and the following two sentences add essential nuance. It is slightly poetic, which may reduce immediate clarity, but still remains efficient and well-structured.

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 rich input schema (14 parameters, 93% described) and the presence of an output schema, the description provides sufficient context for the tool's core purpose and key edge-case semantics (as_of, database-wide filtering). The remaining gaps, such as explicit auth requirements, are already covered by the schema parameter descriptions.

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 high (93%), so the baseline is 3. The description enriches understanding of the as_of and sort/search parameters by clarifying that they apply to the record as it stood on a date and across all rows in the block, which is not fully captured in the individual parameter descriptions.

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 description states what is listed (what you grow, watch for, or saw on a plot) and emphasizes pagination ('a page at a time'), which distinguishes it from saving items or listing blocks. However, it does not contain an explicit verb like 'list' or 'fetch', relying on the title and tool name to convey the operation.

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 tool's resource and intent are implicit from the description, so an agent can infer when to use it for retrieving block items. But it offers no explicit guidance about when to prefer this over sibling tools like goodearth_block_item_save or goodearth_block_list, and no exclusions are stated.

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