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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds meaningful behavior beyond annotations: default mode returns the default form's items in listing order, while all=true returns every form including custom ones with their items.

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 compact and front-loads the purpose, then explains the all flag behavior efficiently. The API endpoint sentence is somewhat extra but still short and potentially useful, so the overall structure is clean without meaningful waste.

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 output schema, the description appropriately explains the returned forms and items for both all=false and all=true. Annotations cover the safety profile, and the low-complexity two-parameter schema is well covered, though pagination or error behavior is not mentioned.

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 both kind and all are already documented in the schema. The description largely mirrors the schema and adds only minor clarification about listing order and items being returned, which is not substantial parameter semantics beyond what is structured.

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 a specific verb and resource: get the membership application forms, scoped by kind company or individual. It clearly distinguishes the company and individual variants, though it does not explicitly contrast itself with sibling tools such as list_application_form_fields or the membership getters.

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?

It explains the all flag behavior, which implies when to use the default versus all-forms mode, but it does not state when this tool should be chosen over alternatives or when-not to use it. The guidance is therefore useful but not explicit about tool selection relative to siblings.

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