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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the trailing "Reads only" is largely redundant with them. The description earns credit by disclosing substantive behavior beyond annotations: diagnostic code issues (bad submit code, unfixed field names, refused fields) with fixes, and month-to-date message counts against the plan cap, which an agent could not infer from schema or annotations.

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?

The purpose is front-loaded in the first clause and every subsequent item describes a real return field, so little is wasted. It is, however, a single very long run-on sentence with stacked parentheticals, which makes it denser than it needs to be for scanning.

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 carries the burden of explaining returns and does so thoroughly, including the plan-cap metric and the fix-oriented code diagnostics. Minor gaps remain: it does not indicate result volume, ordering, or whether forms are paginated, which matters for a site-wide listing.

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?

Only one parameter (projectId) and schema coverage is 100%, with the schema itself pointing to list_projects for the id. The description adds no extra meaning about the parameter, so the baseline 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?

Specific verb ("Lists") plus a scoped resource ("the site's Xodia Forms") that is immediately defined as forms posting to Xodia read in the Content tab, so it is unmistakable versus siblings like list_submissions or list_pages. The enumeration of returned fields (status, file/line, recipients, Turnstile, webhooks, code issues) further pins down what this tool is and is not.

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?

"Read it before changing a form" gives a clear prerequisite/ordering rule that steers the agent to call this before any mutation. It stops short of naming the specific mutation siblings (e.g. connect_form) or stating when listing is unnecessary, so it is strong but not fully explicit about alternatives.

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