List Form Fields

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context—nothing about pagination, filtering, include options, rate limits, or result shape—so it does not enrich the annotation layer.

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 text is short but under-specified, not concise in a useful sense. A single tautological sentence is not appropriately sized for a 29-parameter listing tool with pagination and filtering.

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 29-parameter read-only list tool with 7% schema coverage, the description is far too thin. Output schema and annotations cover return shape and safety, but the agent still lacks the filtering and pagination context needed to call it correctly.

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 only 7% across 29 parameters, and the description adds no parameter meaning. Critical parameters like include, page_size, page_number, and the many filter_* variants are left for the agent to infer from bare names.

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 is a lowercased restatement of the tool name/title ('List form_fields'), so it gives a verb and resource but no scope, content, or distinction from siblings such as list_form_field_options or get_form_field. It is essentially tautological rather than a useful purpose statement.

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?

No when-to-use guidance, alternatives, or exclusions are given. The agent must infer from the name that this is the listing endpoint and cannot tell from the description when to choose it over list_form_field_options, get_form_field, or list_form_sets.

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