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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds the underlying GET path and the fact that results include both auto-flagged and owner-marked spam, which is genuinely useful provenance, but it doesn't discuss paging behavior or response shape beyond the default sort.

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, front-loaded with scope, then the use case, then the equivalence to the sibling. No filler and nothing repeated verbatim from the schema.

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, annotated, fully described 6-param list tool with no output schema, the description covers what the tool returns (spam-flagged or owner-marked submissions, newest first) and how paging mirrors the sibling. Only the response envelope is left implicit, and the schema notes about next_offset and _status partially cover that.

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%, with limit, order, since, offset, columns, and include_delivery_status all documented in-schema. The description only adds a cross-reference ("same filters and paging as formspree_list_submissions") and the spam=true endpoint, adding no syntax or semantics beyond the schema.

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 the submissions") scoped precisely to spam (flagged by Formspree or owner-marked), plus default ordering. It explicitly contrasts itself with formspree_list_submissions, so an agent can tell the two apart without opening a schema.

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?

"Use it to check for false positives" gives a concrete context, and the pointer to formspree_list_submissions for the same filters implies the non-spam alternative. It stops short of an explicit "do not use for X" exclusion, so it's clear but not fully routing.

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