List signup forms

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered (the leading 'Read only' is redundant). Beyond that, the description adds genuinely new behavioral facts: the 20-form result cap and the complete shape of what comes back, which is not available anywhere else since there is no output schema.

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 sentences, front-loaded with the read-only nature and the scope, followed by the field enumeration. The middle field list is dense but each item earns its place because no output schema exists to carry that information.

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 input parameters and no output schema, the description does the only remaining work: it documents the return fields and the result cap, and explains what the returned ids are used for. An agent has everything needed to call it and consume the result.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies the absence of filtering or pagination options by describing a fixed workspace-wide result set.

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?

States a specific verb and resource (list the workspace's signup forms) and bounds the scope with '(at most 20)'. It then enumerates the exact fields returned, so an agent knows precisely what it is asking for and can distinguish it from postfjord_create_signup_form.

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 closing sentence implies the downstream use case ('a form id goes into a landing page form block or an email automation started by that form'), which is helpful chaining context. However, there is no explicit statement of when to call this versus other list tools, and no mention of how the 20-form cap affects callers who expect more.

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