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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new context: default newest-first ordering, the personal-data exposure warning, and the offset/next_offset paging model.

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 sentences plus an endpoint line; the scope and default ordering are front-loaded, and the privacy warning sits next to the columns advice where it is actionable. 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?

For a read-only list tool with full schema coverage and annotations, the description covers defaults, filtering, paging, field selection and data-sensitivity. No output schema exists, yet the shape of a submission ('_date and one value per form field') is described, leaving nothing an agent needs 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 coverage is 100%, so baseline would be 3, but the description adds meaning beyond the schema by explaining when to use 'columns' (privacy-driven minimisation) and the default sort direction. It does not restate limit/offset mechanics, which the schema already documents.

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 (List) and resource (the form's submissions) with an explicit scope note '(not spam)' that separates it from formspree_list_spam_submissions, and names the default ordering. No schema inspection is needed to know what it returns.

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?

Gives concrete guidance for filtering ('Filter by date with since') and paging ('page with limit and offset'), and a conditional recommendation ('ask for the columns you need'). It implies the spam sibling via '(not spam)' but never names it explicitly as an alternative, keeping this at a 4.

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