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

With only readOnlyHint=true provided, the description carries real operational detail beyond the annotation: page size (150), rate pacing under the 5 req/s limit, the max_submissions cap, and the fact that the result reports truncation. It does not say what happens if pagination fails mid-walk or how partial results are handled, so it is strong but not exhaustive.

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 sentences, front-loaded with the pagination mechanism and the cap, followed by the use case. The trailing 'Fillout: GET /forms/{formId}/submissions (repeated)' is slightly redundant but cheap and maps the tool to the underlying API.

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 multi-page export with no output schema, the description discloses the pieces an agent needs: the cap, the pacing, and the truncation signal in the result. It could say more about the returned shape (e.g., a flat list of submission objects) but nothing essential for correct invocation 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 all eight parameters are already documented in the schema. The description only references max_submissions and alludes to the shared filter set; it adds no format or default detail beyond what the schema states, so the baseline 3 applies.

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 and resource (fetch many submissions) and immediately distinguishes itself from the sibling by mechanism: multi-call offset pagination at 150/page, capped by max_submissions. An agent can tell it apart from fillout_list_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?

'Use this for analysis across a whole response set' gives a clear selection context, and 'Same filters as fillout_list_submissions' implicitly routes the agent to that sibling for small scoped reads. It stops short of an explicit when-not rule (e.g., 'use list_submissions for a single page'), so it is clear but not fully prescriptive.

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