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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds important context: FREE businesses cannot use this tool, and it requires prior access checks. It does not describe the return format or side effects, but for a read-only analytics tool, the behavioral disclosure is adequate and consistent.

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 sentences but contains imperative instructions that could be more concise. The first sentence clearly states the purpose, but the second is a long list of prerequisites. It is not overly long, but some of the instructions feel verbose.

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?

Given 5 parameters with no descriptions and no output schema, the description should explain what analytics are returned and how to specify the date range. It fails to do so, leaving the agent underinformed about expected inputs and outputs.

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 does not explain any of the 5 parameters (e.g., communityId, formId, startDate, endDate, lastXDays). The agent has no guidance on what values to provide or how date ranges work, severely impacting correct invocation.

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 tool gets analytics for a lead form. It uses a specific verb ('Get analytics') and resource ('lead form'), distinguishing it from sibling tools like get_lead_form (which likely returns the form itself) or get_lead_form_applicant_activity.

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 provides explicit instructions: check business permissions, FREE businesses cannot use, call check_business_tool_access first, show grace-period warnings and resubscribe link. It tells the agent when not to proceed. However, it does not compare this tool to alternatives (e.g., when to use get_lead_form_analytics vs get_lead_form_submission).

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