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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value by specifying the allowed state values ('ready', 'processing', 'failed', 'all') and the pagination mechanism (cursor), which go beyond annotations. It does not contradict the annotations.

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 two short sentences that front-load the resource ('Forms in the user's Emboss library') and then detail state and pagination. There is no fluff or redundant wording, making it efficient and easy to scan. It could be slightly clearer by adding 'List' at the start, but it is concise.

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 listing tool, the description covers the state filter and pagination, while the output schema documents the return format and annotations cover safety. However, the limit parameter is not explained, and there is no mention of default behavior beyond the schema defaults. This is adequate but leaves a minor gap in understanding all parameters.

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?

With schema description coverage at 0%, the description must explain parameters. It explicitly lists the state values and mentions cursor for pagination, but does not explain the limit parameter, leaving its meaning to common sense. This partial coverage compensates somewhat but is not complete for all three parameters.

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 states that the tool returns forms in the user's Emboss library, which implies a listing operation. It adds state filtering and pagination details, distinguishing it from single-form tools like get_form or find_form, though not explicitly naming them. The purpose is clear and specific enough for an agent to understand it lists forms.

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 no guidance on when to use this tool versus alternatives such as find_form or get_form. It only mentions filtering by state and pagination, but does not state when listing is appropriate or when to prefer another sibling. This is implied but not explicit, leaving the agent to infer usage.

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