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 usefully discloses the return shape ({EntryCount}) and the underlying endpoint, which matters since there is no output schema, but it adds nothing about permissions or limits. This is modest added value on top of annotations, not rich behavioral context.

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 short sentences, front-loaded with the action and immediately followed by the return shape and endpoint. No filler, every clause 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?

For a single-parameter read-only count, the description plus full schema coverage and the readOnlyHint leave little ambiguity about correct invocation. The only gap is a cross-reference to wufoo_list_report_entries for the list-vs-count decision, which is a minor omission rather than a blocking one.

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?

Only one parameter exists and schema description coverage is 100%: the schema itself documents the report identifier format, length bounds, and points at wufoo_list_reports. The description mentions '{identifier}' in the endpoint string but adds no new meaning — baseline 3 is correct when the schema does all the work.

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?

'Count the entries in a report' states a specific verb (count) plus resource (report entries), and the 'report' scope cleanly separates it from the sibling wufoo_count_form_entries and wufoo_count_form_comments. An agent knows exactly what is counted without opening the 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?

The description says what the tool does but never says when to use it versus wufoo_list_report_entries (list vs count) or the form-level count sibling. No prerequisites, no exclusions, no alternative routing — the agent must infer the choice from the name alone.

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