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

Annotations declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context about business permission checks and free-tier restrictions, which is valuable beyond annotations. However, it does not mention pagination behavior or other API traits.

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 concise: one sentence for purpose, then concise usage instructions. It is front-loaded and every sentence provides essential information. Slightly wordy in the guidelines, but acceptable.

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?

No output schema, and the description does not describe return format or pagination behavior. Given the pagination parameters (pageNo, pageSize), this is a gap. However, the description covers purpose and usage well for a simple listing tool.

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%. The description fails to explain any of the three parameters (pageNo, pageSize, communityId). Baseline for 0% coverage is 4 if description compensates, but it doesn't, leaving the agent without meaning for each parameter.

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 the verb 'list' and the resource 'available lead form style presets for a community managed by the authenticated Nas.com user'. It is specific and distinguishes from sibling tools like list_lead_form_applicants or list_magic_content_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 when-to-use guidance: check business permissions first, FREE businesses cannot use, call check_business_tool_access, handle grace-period warnings. This clearly instructs the agent on prerequisites and conditions for invocation.

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