get-form-entries

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

The term 'List' implies a read-only operation, but with no annotations, the description alone carries the burden. It does not disclose pagination behavior, default limits, or potential edge cases like empty results. The schema covers fetch_all, but the description itself stays minimal.

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 that conveys the primary purpose and output shape without any redundancy or irrelevant details.

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?

No output schema exists, so the description should convey return shape; it does so by mentioning label/value pairs and the linked matter. Pagination limits and ordering are absent, but for a simple listing tool the description is largely complete.

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 67%, so form_uuid and fetch_all are explained, but the 'page' parameter lacks a description and the tool description does not compensate. The description adds no semantic detail about parameters, though form_uuid is implied by 'for a custom form'.

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 clearly states a specific action ('List submissions'), identifies the resource ('custom form'), and adds output detail ('label/value pairs and the matter it created'). This distinguishes it from siblings like 'get-form' (which retrieves the form definition) and 'submit-form' (which creates 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?

The wording 'List submissions for a custom form' gives clear context for when to use the tool, implying it is for viewing entries rather than managing forms. However, it does not explicitly exclude alternatives or name related tools such as 'get-form' or 'list-forms'.

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