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

Annotations only declare readOnlyHint, so the description carries most of the burden and delivers: it discloses that checkbox/name/address/likert fields nest SubFields and that choice-style fields nest Choices, and that admin-only fields are omitted. This is meaningful return-shape behavior beyond the annotations, though pagination/error/rate behavior is unaddressed.

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?

A single dense sentence front-loads the resource and then systematically enumerates attributes and nesting rules with zero filler. It is packed but every clause carries information; the endpoint reference is a compact addition.

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 convey the return shape, which it does by listing field attributes and nested SubFields/Choices. It omits any note on how the `system` parameter alters the payload, but overall it is sufficient for correct invocation and interpretation.

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%, so both parameters are fully documented in the schema, establishing the baseline of 3. The description adds nothing about the `system` flag and only reinforces the form-identifier semantics already covered by 'See wufoo_list_forms' in the schema.

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 and scope: 'the field structure of a form,' then enumerates the attributes returned (Title, Type, API ID, required flag, default, page). It is distinguishable from wufoo_get_form (metadata) and wufoo_get_report_fields by the 'form' + 'fields' framing, though it never names a sibling explicitly.

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 explicit when-to-use or when-not-to-use guidance. Usage is only implied by the note that the API ID is 'used for filters, sorting and submissions,' which hints at why an agent fetches fields, but the tool is never contrasted with alternatives like wufoo_get_form or wufoo_get_report_fields.

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