list_observations

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

No annotations are supplied, so the description bears the full behavioral burden. "List" implies a non-mutating read, but nothing is said about ordering, pagination/limits, permissions, or what population is returned when the filter is omitted; with zero annotation coverage these are real gaps, only partly offset by the existence of an output 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?

One short sentence with the action front-loaded and no filler. It is efficient, though the terseness leaves no room for the qualifiers that would make it more informative.

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 single-optional-parameter list tool with an output schema covering return values, the description is minimally sufficient to call the tool. It still omits result ordering, result volume, and the default behavior with no filter, which matter for a listing operation.

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 0%, so the single parameter planting_id is documented only by its title and type. The description partly compensates by stating the filter narrows results to "one planting," which conveys the semantics of that argument, though it does not state whether the id must reference an existing planting or how invalid ids behave.

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?

"List observations" gives a specific verb and resource, and the qualifier "optionally filtered to one planting" bounds the scope. It is clearly a read operation distinct from log_observation by naming convention, but it never explicitly says how it differs from siblings like list_plantings.

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?

Usage is only implied: the phrase "optionally filtered to one planting" hints that the filter is for narrowing to a single planting, and the absence of required parameters signals a broad listing call. There is no explicit when-to-use, when-not-to-use, or pointer to alternative tools for related data.

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