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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: entries are keyed by field API ID (like a datagrid/export view) and no paging or filter parameters are documented, which saves an agent from futile attempts. It stops short of describing result volume or ordering.

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?

Two sentences plus an endpoint reference, all front-loaded with the essential meaning first. Slightly boilerplate in the trailing endpoint citation, but nothing wasteful.

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 gives the agent a mental model of the return value (entry data keyed by field API ID, matching datagrid/export output) and notes the lack of paging. Enough to call it correctly; only result volume and ordering remain unaddressed.

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%, with both parameters fully documented in the schema (including the pointer to wufoo_list_reports for the report identifier). The description adds marginal value by noting the keying and the absence of documented paging/filter params, but nothing beyond the schema's own field semantics.

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?

Names the specific resource (the entries that make up a report) and pins down its shape: what the datagrid widget or an export would show, keyed by field API ID. That clearly separates it from siblings like wufoo_list_form_entries, wufoo_get_labeled_entries, and wufoo_list_report_widgets.

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?

Usage is implied by the resource (report entries rather than form entries), and the note that Wufoo documents no paging or filter parameters usefully constrains what an agent should attempt. However, it never explicitly states when to prefer this over wufoo_list_form_entries or wufoo_get_labeled_entries.

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