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

readOnlyHint=true already establishes the safety profile, but the description adds real behavioral context beyond annotations: keys are remapped, default/system keys (EntryId, DateCreated) are left alone, empty values are dropped unless includeEmpty is set, and a fieldIds map is returned. It does not cover rate limits or error behavior, so it falls short of exhaustive, but it meaningfully enriches the annotation.

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 dense but front-loaded: the transformation (the reason to call this tool) comes first, followed by defaults, then return contents. The inline examples add length but also precision. It is slightly heavy for a single paragraph but no sentence is filler.

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 carries the burden of describing returns, and it does: entries keyed by title, preserved system keys, dropped empties, plus fieldIds. Combined with 100% schema coverage for the 9 parameters and readOnlyHint, an agent has everything 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 coverage is 100%, so the baseline is 3, and the description rises above it: it explains the includeEmpty default interplay with dropped empty values and explains what fieldIds is for (building filters or submissions). The cross-reference to wufoo_list_form_entries also tells the agent the paging/sort/filter parameters behave identically.

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 states a specific verb (fetch a page of entries) plus the distinctive transformation that defines this tool: every Field### key replaced by its human title, with sub-field naming rules. That transformation is exactly what separates it from the sibling wufoo_list_form_entries, so an agent can route between them without opening a schema.

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?

It says it "takes the same paging, sorting and filter arguments as wufoo_list_form_entries," which references the alternative but only for argument reuse, not for routing. There is no explicit statement of when to pick this tool over wufoo_list_form_entries or when the title-keyed view is undesirable (e.g. numeric key stability), so usage is implied rather than guided.

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