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 still adds value by disclosing the scope (one form at a time), the fields returned, and the filterable dimensions. It stops short of describing pagination behavior for the paged result set, which is a minor gap.

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 tight fragments: what is returned, how it can be filtered, and the endpoint. Content is front-loaded and no sentence is redundant.

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 usefully sketches the response shape (submitter, timestamp, answers, status/owner/notes) and the filtering surface for a 6-parameter tool. It is slightly thin on how the return payload is structured and on pagination semantics, but the schema covers those inputs.

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 parameter (limit, offset, form_id, user_ids, submitted_to/from) is already documented in the schema. The description's "filter by submitting users and time window" only restates two of those filters without adding format or boundary semantics, so the baseline of 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?

The description gives a specific verb (list) and a precisely scoped resource (submissions of one form), and even enumerates what each submission contains (submitter, timestamp, answers, manager fields). This clearly separates it from siblings like connecteam_list_forms and connecteam_list_tasks.

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?

It states the available narrowing criteria (submitting users, time window), which implies how to use it, but never says when to choose this over a sibling or what prerequisites exist (e.g., that a form_id comes from connecteam_list_forms). Usage is implied rather than stated.

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