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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the description's 'Read-only' sentence merely restates structured data rather than adding to it. Nothing is said about default page size, maximum limit, ordering of results, or what a page beyond the last returns — the behavioral gaps an agent would actually hit.

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 sentences, front-loaded with the resource being listed, with no filler. The only slack is the 'Read-only' clause, which duplicates the annotation already visible to the agent.

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 two-optional-parameter read operation with no output schema, the definition is minimally adequate but leaves the agent guessing about return shape, pagination defaults, and total-count behavior. Given the absence of an output schema, a sentence on what a listing returns would have closed the gap.

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%, with 'page' and 'limit' documented in the schema, so the baseline of 3 applies. The description only repeats that limit and page are supported, adding no format, default, or range 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 names a specific verb and resource ('List all webforms in your MailerCloud account'), so an agent immediately knows it enumerates webforms. It does not need to disambiguate against siblings because no other webform tool exists in the toolset, but it also doesn't state scope relative to the account's other list_* tools.

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?

Usage is implied by the verb 'List' — call this when you need the webforms in the account. There is no explicit when-to-use versus alternatives guidance, no mention of prerequisites (e.g., whether webforms must exist or be enabled), and no note on when pagination should be employed.

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