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

Annotations only cover read-only safety, and the description carries the rest: empty/null values are dropped unless includeEmpty is set, EntryId/DateCreated and other system keys are preserved, sub-field keys follow a 'Title — Label' convention, and an extra fieldIds (title → API ID) map is returned. It also discloses the underlying two-call (fields.json + entries.json) behavior, which is meaningful for performance expectations.

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-loads the core differentiator (title-keyed entries) before secondary details, and each sentence carries distinct information: key conventions, default-key preservation, empty handling, fieldIds return, argument parity with the sibling, and the endpoint. Dense but not padded.

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 9 parameters fully covered by the schema and no output schema, the description fills the remaining gap by describing the shape of the response (title-keyed entries, retained system keys, dropped empties, fieldIds map) and the source endpoints. An agent has enough to call it correctly and interpret results.

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 the schema already documents form, sort, match, system, filters, pageSize, pageStart, includeEmpty and sortDirection. The description defers parameter behavior to wufoo_list_form_entries rather than restating syntax, adding only the practical link that the returned fieldIds help build filters/submissions. Baseline 3 is appropriate.

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 ('Fetch a page of a form's entries') and immediately names the transformation that distinguishes it from siblings: Field### keys replaced by human titles. The contrast with wufoo_list_form_entries is explicit, so an agent can route between them without opening schemas.

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?

Names a sibling (wufoo_list_form_entries) and states this tool takes the same paging/sorting/filter arguments, which frames the relationship and implies when to pick this variant. It stops short of an explicit 'use this instead of X when you need titles' conditional, so it is clear context rather than full when/when-not guidance.

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