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

Annotations already establish readOnlyHint=true, so safety is covered. The description adds that entry responses are keyed by field_id, which is genuinely useful behavioral context, but says nothing about volume, pagination, or error behavior for a per-form listing.

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 sentences, front-loaded with what is returned, then the consumer-facing note about field_ids. The trailing 'Breeze: GET /api/forms/list_form_fields' is marginal but compact and does not obscure the substance.

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 single-parameter read-only tool with no output schema, the description usefully enumerates returned attributes and explains how the results are consumed downstream. Only volume/pagination expectations remain unaddressed.

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 100% — form_id is already documented as the numeric Breeze id of the form. The description adds no syntax, format, or constraint detail beyond what the schema provides, so the baseline 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?

States a specific verb+resource: lists the fields belonging to one form, and enumerates what each item contains (field_id, field_type, name, options). This distinguishes it from breeze_list_forms (forms themselves) and breeze_list_form_entries (entry data), though the differentiation is implied rather than stated.

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 note that 'form entry responses are keyed by these field_ids' implies the tool's purpose (mapping entry values back to human-readable fields), which is useful contextual guidance. However, there is no explicit when-to-use vs. when-not, and no named alternative such as breeze_list_forms.

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