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

Beyond the read-only/idempotent annotations, the description discloses useful behavior: results are newest first, reading does not mark items read, webhook delivery states are included, and submissionId returns a richer single record with arrival context and notes. These details go well beyond what the annotations and schema provide.

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?

The description is compact and front-loaded: it leads with the resource and ordering, then explains the single-record mode, filters, and the read side effect. The field list and webhook-status detail are dense but directly useful.

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 supplies the key return shape and ordering, plus the special single-submission behavior and read side effect. Pagination details are left to the schema's cursor/limit fields, which is appropriate.

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 coverage is 100%, so the baseline is 3, but the description adds meaning by grouping the filters, restating the open default, and explaining that submissionId switches to a full single-submission view. It does not explain limit/cursor/id, but the schema already documents those adequately.

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 states a specific resource — the site's form inbox of visitor answers — and specifies ordering, returned fields, and the single-submission mode. It is clearly distinguishable from sibling tools such as list_form_webhooks, even though it mentions webhook delivery status as part of each submission.

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 explains the main usage modes: list with optional state/formName/q filters, defaulting to open, or fetch one full submission via submissionId. It also notes that reading does not mark submissions read. It does not explicitly name alternatives or when not to use it, but the operational context is clear.

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