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

Annotations indicate write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). Description adds that it auto-resolves template and requires permission checks. Does not detail output or side effects, but sufficient for a draft creation tool.

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?

Four sentences, each essential. Front-loaded with purpose, then critical guidelines. No redundant or vague phrases.

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?

Covers purpose, prerequisites, and auto-resolution. However, lacks description of output (draft lead form) and what to do with it. No output schema, so more context would help agent understand return value.

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 coverage is 0%, and description does not explain any of the 4 parameters (communityId, goal, prompt, customGoal). Only implicit guidance about not needing template id. Fails to add meaningful parameter context.

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?

Clearly states it generates a draft lead form for a community. Verb 'generate' and resource 'lead form' are specific. Distinguishes from siblings like publish_lead_form, delete_lead_form by focusing on creation of a draft.

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?

Explicitly tells when to use: before offering, check business permissions; FREE businesses cannot use; call check_business_tool_access; show grace-period warnings and verified resubscribe link; never proceed when blocked. Also says not to ask for template id, as it auto-resolves.

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