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

readOnlyHint=true already establishes the safe-read profile, so the bar is lower. The description adds genuine behavioral context beyond annotations: offset pagination and the fact that the response carries totalResponses and pageCount. It stops short of noting rate limits or the 150-per-page ceiling behavior.

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 tightly packed sentences with the core purpose front-loaded, followed by pagination/return behavior and the underlying endpoint. The parenthetical field enumeration is dense but each element earns its place by clarifying return payload.

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 present, the description compensates by naming the return metadata (totalResponses, pageCount) and the pagination model, and it covers the filter dimensions. For a 10-parameter read tool this is complete enough for correct invocation.

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 every one of the 10 parameters is already documented in the schema. The description restates the filter categories (date range, status, free-text search) without adding syntax, defaults, or edge-case meaning beyond what the schema provides. 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 (List) and resource (a form's submissions) with explicit scope ('one page') and enumerates what each submission contains. An agent can distinguish this from fillout_count_submissions and fillout_get_submission 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?

The description conveys the context (paginated listing with filters by date range, status, or free-text search), which implies when to reach for it. However, it never explicitly contrasts itself with the sibling alternatives like fillout_count_submissions or fillout_export_submissions, leaving the routing to inference.

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