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

Goes well beyond the readOnlyHint annotation: page size (150), rate pacing under Fillout's 5 req/s limit, the max_submissions cap, and that the result reports truncation. These are exactly the operational traits an agent needs before calling a multi-page read.

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 dense sentences, each carrying distinct information: mechanism/limits, filter equivalence, and intended use plus truncation signal. Front-loaded with the operation and its caps; no filler.

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 compensates by noting the truncation flag and the paginated fetch behavior, which covers the key return-side concern. It stops short of describing the response envelope (submission shape, pagination offsets) that an agent might want, so it is strong but not exhaustive.

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, making the baseline 3. The description only adds the semantics of max_submissions and the filter-sharing note, adding little beyond the schema.

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?

Specific verb + resource + mechanism: 'Fetch many submissions in one call by walking the offset pagination'. It clearly separates itself from fillout_list_submissions (bulk export vs. listing) and from fillout_count_submissions by naming the sibling it shares filters with.

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?

Explicitly scopes the use case ('Use this for analysis across a whole response set') and ties the filters to fillout_list_submissions. It does not state when NOT to use it (e.g., fetch a single submission via fillout_get_submission), so it falls short of full when/when-not guidance.

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