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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds meaningful non-annotation behavior: entitlement gating, that FREE businesses are excluded regardless of feature rows, the required access-check call, and the grace-period/resubscribe flow. It says nothing about ordering, result shape, or pagination behavior, which keeps it short of a 5.

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 purpose is front-loaded in one clear sentence, but the remaining four sentences are access-control boilerplate that restates the same idea ('check business permissions' then 'Call check_business_tool_access'), suggesting tool-agnostic text appended to many definitions. Nothing is off-topic, yet the permission block is disproportionately long relative to the one-line purpose.

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 read-only paginated list tool with a fully described three-parameter schema and no output schema, an agent has what it needs: what it returns conceptually, the required communityId, and the entitlement preconditions. Adding a note on preset ordering or typical use in update_lead_form_style_preset would make it fully self-sufficient.

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 pageNo, pageSize, and communityId are already documented, and the description adds no further meaning about them. The one hint ('for a community') merely echoes the existing communityId description. Baseline 3 applies when the schema carries the load.

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 first sentence gives a specific verb and resource ('List available lead form style presets') and scopes it to a community managed by the authenticated user, which separates it from mutation siblings like update_lead_form_style_preset. It does not explicitly name a confusable alternative (e.g. list_magic_content_styles), so differentiation is achieved by scope wording rather than direct routing.

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?

There is strong guidance on prerequisites and gating ('Call check_business_tool_access before collecting inputs', never proceed when access is blocked), which is real when-to-use context. However, it never states when to pick this tool over the style-related siblings or what the presets are used for downstream, so alternative selection is left implicit.

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