list_forms

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation context: that returned data includes submission counts/last-submission timestamps, and that the data touches visitor personal data behind an Admin/Editor permission. It doesn't discuss pagination or limits, but it goes well beyond restating the 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?

Three sentences, front-loaded with the resource and return fields, followed by the routing rule and then the permission/sensitivity note. Every sentence carries distinct, actionable information with no filler.

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 compensates by enumerating the returned fields. It also covers permission requirements, data sensitivity, and relative ordering versus sibling form tools, while the schema handles the site-default behavior. An agent has everything needed to call this correctly.

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% and the single 'site' parameter is documented in the schema with multisite/default-site guidance and a pointer to list_sites. The description adds nothing about the 'site' parameter, so the schema carries the full burden and 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+resource ('List the forms (Form blocks) in this site') and it enumerates the fields returned (formId, name, submission count, last submission time). It clearly distinguishes itself from sibling tools like list_form_submissions and export_form_submissions by positioning itself as the enumeration step.

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?

It explicitly says to use this 'before list_form_submissions or export_form_submissions', giving the agent a clear entry-point rule, and it names the required permission (submission.read, Admin/Editor) with the reason (visitor personal data). Both the when-to-use condition and the prerequisites are stated.

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