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

Annotations already declare readOnlyHint=true, so safety is covered. The description goes further by disclosing the return shape ({EntryCount}) and the underlying endpoint, plus the fact that filters reuse the list_form_entries convention — genuinely useful context beyond 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?

Three compact sentences, front-loaded with the operation and scope, then use case, then return contract. Nothing is redundant and every sentence earns its place.

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?

Covers the operation, its filtering scope, the return field, and the endpoint for a read-only count tool with only one required parameter. Since readOnlyHint is set and the return value is stated, nothing an agent needs to call it correctly is missing.

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 the schema fully documents form, match, and filters. The description adds a cross-reference to wufoo_list_form_entries for filter format, but no additional syntax or semantics beyond that; baseline 3 is appropriate when the schema carries the load.

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 a specific verb (Count) and resource (form entries) and immediately scopes it: all entries or only those matching filters. Distinguishes itself from siblings like wufoo_count_form_comments and wufoo_count_report_entries by targeting form entries specifically.

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?

States the practical purpose explicitly — 'Useful to plan paging' — which tells the agent when to reach for it, and points to wufoo_list_form_entries as the source of the matching filter format. It lacks an explicit when-not or a note on when a full list is preferred, so it falls short of a 5.

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