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

readOnlyHint already covers the safety profile, and the description adds genuinely new behavioral context: admin-only fields are excluded, certain field types carry nested SubFields or Choices, and the API ID format (Field###) is what filters, sorting and submissions consume. It does not disclose pagination or error behavior, but for a read-endpoint this is well above the annotation baseline.

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?

Front-loaded with the core payload (field structure) then details of returned attributes, edge cases, and the API endpoint. Dense but each clause carries information; only the trailing Wufoo endpoint line is arguably redundant.

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 must describe return values, and it does so thoroughly — field attributes, nested SubFields and Choices by field type, and the admin-field exclusion. It misses only usage/prerequisite context, which is minor for a read 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 both parameters (form, system) are fully documented in the schema, including examples and the pointer to wufoo_list_forms. The description does not add syntax or format detail beyond that, 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 and resource — retrieving the field structure of a form — and enumerates exactly what is returned (Title, Type, API ID, required flag, default value, page, SubFields, Choices). It is clearly distinct from wufoo_get_form metadata, but it never names that or any other sibling, so differentiation 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?

There is no when-to-use or when-not-to-use guidance. Nothing tells the agent when to prefer this over wufoo_get_form or wufoo_get_report_fields, nor any prerequisite for obtaining the form identifier.

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