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

Annotations already declare readOnlyHint=true, and the description is consistent with that safety profile by naming the underlying GET endpoint. Beyond annotations it adds real context: the entry shape (id, created_on, person_id) and the conditional behavior that details=true keys responses by form field_id.

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?

Effectively one dense sentence plus an endpoint tag, front-loaded on the resource before the conditional details behavior. Parentheticals carry useful payload rather than filler, though the sentence is packed and slightly hard to parse on first read.

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 no output schema, the description correctly takes on the return-shape burden and does so for both the default and details=true modes. It omits pagination/result-limit behavior and whether entries can be empty, which are the remaining gaps for a listing tool.

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 100%, so the baseline is 3, but the description goes further than the schema text by explaining that details=true produces responses keyed by form field_id and pointing at breeze_list_form_fields for interpreting those keys.

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 resource ('Submissions to one form') with a concrete verb and enumerates the returned identity fields (id, created_on, person_id). It also cross-references breeze_list_form_fields, so an agent can tell entries apart from fields without opening either schema.

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: it is a per-form listing, so form_id is mandatory, and details=true is described as the richer mode. There is no explicit when-to-use/when-not or routing to alternatives such as breeze_list_forms, and the breeze_list_form_fields mention reads as a 'see also' rather than an alternative.

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