List forms

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral detail such as pagination and the fact that forms reference templates, but it does not disclose defaults, ordering, or response characteristics beyond that.

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?

Two short, focused paragraphs with no filler. The first sentence states the core purpose, and the second provides valuable follow-up guidance about template references and when to fetch form details. Every sentence earns its place.

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?

For a simple paginated list tool with complete schema coverage and read-only annotations, the description is largely sufficient. It explains the resource, scope, pagination, and what the list items contain. A slightly more explicit pointer to the exact sibling tool would make it fully 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 100%, so the schema already documents all three parameters. The description reinforces that profileUuid refers to the profile and that the result is paginated, which maps to page/per_page, but it adds no new parameter-level meaning beyond the schema.

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 the tool's action and resource: 'Get a paginated list of the signup forms in a profile.' It is specific enough to distinguish this from sibling tools like reach_getFormDetailsV1 and reach_deleteFormV1, which concern individual forms or destructive operations.

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 description gives clear context for when this list tool is appropriate and subtly routes the agent to a separate details operation: 'Get the form details for a directly usable template URL and for the tags...' It does not explicitly name the sibling tool or state when not to use it, so it stops short of a 5.

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