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

Annotations declare readOnlyHint=true and destructiveHint=false, so the tool is read-only. The description adds value by disclosing business access restrictions and requirement to check permissions, which is beyond what annotations provide. However, it doesn't describe the output format or pagination behavior.

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 a few sentences but includes redundant guidance about checking permissions. It is front-loaded with the purpose but could be more concise. Generally acceptable but not tight.

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?

The tool has 6 parameters including pagination (pageNo, pageSize) and filtering (search, filters), plus no output schema. The description focuses on permissions but fails to explain how listing works, pagination, or return value. This leaves significant gaps for the agent.

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 0%, and the description adds no information about the 6 parameters (communityId, formId, pageNo, etc.). It only mentions 'inputs' generically. The agent gets no help understanding what each parameter means from the description.

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 it lists applicants submitted to a lead form, using specific verb and resource. This distinguishes it from other list tools like list_magic_ads_leads or list_lead_form_styles.

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?

Provides explicit guidance: check business permissions before offering, notes free businesses cannot use, instructs to call check_business_tool_access, and explains handling of grace-period warnings and resubscribe links. This tells the agent when to use and what prerequisites are needed.

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