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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured context: results are ordered newest first, field values are untrusted text authored by members of the public (a prompt-injection warning), and visitor IP addresses are deliberately excluded. It does not describe default/max result size or pagination behavior.

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 sentences, each load-bearing: purpose plus ordering first, then the untrusted-content warning, then the IP-exclusion note. No repetition of what the schema or annotations already say.

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 still tells the agent enough about the return shape (newest-first messages, untrusted text fields, no IPs) to consume results safely, and the schema supplies pagination. A brief note on default page size or how to detect the last page would close the remaining gap.

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 form filtering, the 1-50 limit, the site name, and the 'before' cursor. The description adds no parameter-level meaning beyond the 'newest first' ordering that contextualizes the cursor. Baseline 3 when the schema carries the full parameter burden.

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 (Lists) and resource (messages sent through a Pagehaus site's contact forms) plus ordering (newest first). This is trivially distinguishable from siblings like list_files, list_activity, and list_sites, which target entirely different resources.

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 resource description (read contact-form submissions), but there is no explicit when-to-use or when-not-to-use guidance and no named alternative among the eleven siblings. The API help URL gives provenance but not routing criteria.

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