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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds real value beyond that by disclosing the return shape (field_id, field_type, name, options) and the keying relationship to form-entry responses. For a read-only listing tool this is close to complete, missing only pagination/volume behavior.

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?

Three short, front-loaded sentences with no filler; the returned fields are stated before the supporting rationale. The trailing endpoint string ('Breeze: GET /api/forms/list_form_fields') is mildly redundant but inexpensive.

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 carries the burden of describing the return and it does so by listing the field attributes and their role as keys for form entries. For a single-parameter, read-only list tool, what the agent needs to call it correctly is essentially present.

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?

There is one parameter with 100% schema description coverage, so the schema already explains that form_id is the numeric Breeze id of the form. The description adds no numeric-format or validation detail beyond that, so the baseline of 3 applies.

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 names the resource (one form's fields) and even enumerates the returned attributes (field_id, field_type, name, options), which is more than the title alone conveys. The verb 'list' is only implied, and the distinction from the nearby siblings breeze_list_forms and breeze_list_form_entries is left to inference.

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 implied rather than stated: the note that 'form entry responses are keyed by these field_ids' tells the agent why field_ids matter when working with entries, which is genuine contextual guidance. However there is no explicit when-to-use, prerequisites, or routing to an alternative sibling.

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