wp_list_form_submissions

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

No annotations are provided, so the description carries the full behavioral burden. It only states that it lists submissions, without disclosing return format, pagination behavior, ordering, or possible side effects. 'List' implies read-only, but this is left implicit.

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 description is a single, front-loaded sentence with no filler. Every word contributes meaning, and it delivers the core action efficiently.

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?

This is a minimal description with no output schema and no annotation context. It omits pagination parameter semantics, return value shape, and the relationship to form-related sibling tools like wp_list_forms. Basic invocation is possible, but an agent is left guessing about important details.

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 'id' is described in the schema (as 'Form ID'), and the description does not explain 'page' or 'per_page'. With schema description coverage at only 33%, the description should compensate by clarifying the pagination parameters, but it does not.

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?

The description uses a specific verb ('List') and resource ('submissions for a Ninja Form'), making the tool's purpose immediately clear. It also distinguishes itself from all sibling tools, none of which mention submissions.

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?

There is no guidance on when to use this tool versus alternatives, no mention that a form ID must first be obtained via wp_list_forms or wp_get_form, and no exclusions or fallback tools. The usage context is entirely unstated.

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