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

'Read-only. Does not charge.' largely restates the readOnlyHint and destructiveHint=false annotations already supplied, earning little extra credit. The '(needs account token)' note does add real, non-annotated context about authentication, and 'Latest' hints at ordering, which keeps this above a bare restatement.

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 the prerequisite and the resource. Minimal waste, though the 'Read-only' sentence is redundant against the annotations and could be dropped.

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 two-parameter read-only list tool with full schema coverage and no output schema, the description is adequate. The gap is the unresolved overlap with list_form_submissions and the absence of any pagination or return-shape note, which the annotations do not cover.

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 the schema already documents both 'site' (with an example address) and 'limit'. The description's 'limit is how many to return, at most 50' duplicates the schema text verbatim without adding format or edge-case meaning, so the baseline of 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?

It names a concrete resource ('Latest form messages for one claimed site'), so an agent knows what it retrieves. However, the sibling tool list_form_submissions covers closely overlapping territory and the description makes no attempt to distinguish the two, leaving 'leads' vs 'submissions' ambiguous.

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?

The only guidance is the parenthetical prerequisite '(needs account token)', which is a precondition rather than a usage rule. There is no statement of when to pick this over list_form_submissions or any other listing tool, and no exclusions.

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