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

With no annotations, the description carries the burden and does disclose two non-obvious traits: spam is excluded unless status='spam', and a paid plan is required. These are meaningful behavioral/auth facts not derivable from the schema. It stops short of describing pagination behavior or return shape, so it isn't fully complete.

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?

Two tight sentences: purpose and scope first, then the filter inventory, then the spam and plan caveats. Front-loaded and free of filler, though the parenthetical filter list is dense.

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 an 11-parameter read tool with no annotations and no output schema, the description covers purpose, filters, spam behavior, and plan gating. It still leaves pagination mechanics, sort options, and several parameter semantics unaddressed, so gaps remain given the low schema coverage.

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 45% (below 50%), so the description should compensate more than it does. It maps filters to status, date range, text search, country, attachments, and failed deliveries, but leaves sort, limit, offset, and formId semantics unexplained (limit max 100, offset paging, enum values).

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 (read/list) and resource (submissions) with explicit scope ('across the workspace or for one form') and enumerates the supported filters. It is clearly distinguishable from get_submission (single), delete_submissions (removal), and export_submissions, though it doesn't name any sibling to contrast itself.

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?

Usage is implied by the scope statement and the list of filters, and it notes the paid-plan prerequisite. However, it gives no explicit when-to-use-vs-when-not guidance and never names an alternative tool (e.g. get_submission_stats or export_submissions) for adjacent needs.

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