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

readOnlyHint=true already tells the agent this is a safe read. The description adds that questions are returned alongside forms and gives the underlying endpoint, which is mild extra context. It says nothing about pagination behavior or result size, so it does not go far beyond the annotations.

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 short sentences with the core purpose front-loaded and no filler. The trailing raw endpoint path (GET /forms/v1/forms) is the least valuable element but costs little.

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 simple, zero-required-parameter list tool with full schema coverage and readOnly annotations, the description covers purpose, content of the response (forms with questions) and filterability. With no output schema, a brief note on return shape beyond "with their questions" and pagination would round it out, but nothing critical 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 five parameters are already documented in the schema with formats, defaults and bounds. The description only restates that name and creation-date filtering exist, adding no syntax or semantics beyond the schema; 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 (list forms) and clarifies the domain with examples — checklists, inspections, reports — plus the notable fact that questions are included. It does not explicitly distinguish itself from the closest sibling, connecteam_list_form_submissions, though the noun difference makes the split inferable.

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?

"Filter by name or creation date" implies how to narrow results, but there is no statement of when to reach for this tool versus connecteam_list_form_submissions or when not to use it. Usage is inferable from the name rather than given.

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