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

Annotations are minimal (readOnlyHint: false, destructiveHint: false). The description discloses that if the form uses a default style, the tool creates a custom style and attaches it. This adds behavioral context beyond annotations, though it does not detail all effects (e.g., overwriting existing custom styles).

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 moderately concise, front-loading the purpose in the first sentence. The subsequent sentences add necessary usage constraints. It is slightly long but every sentence serves a purpose, making it well-structured.

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 the tool has 6 required parameters, nested objects, and no output schema, the description is incomplete. It lacks details on parameter semantics, acceptable values, and return behavior. The only behavioral insight is the default style creation. More information is needed for full autonomous usage.

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?

The input schema has 0% description coverage, and the description does not explain any of the 6 required parameters (communityId, formId, typography, color, button, borderRadius). It only generically mentions 'style', leaving the agent without guidance on how to populate these nested object parameters.

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's purpose: 'Update the style for a lead form.' It distinguishes from siblings like update_lead_form_style_preset by focusing on style customization. The mention of creating a custom style when using a default one adds specificity.

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 preconditions: check business permissions, FREE businesses cannot use, call check_business_tool_access, and handle grace-period warnings. It does not directly compare to alternative tools like update_lead_form_style_preset but gives clear when-to-use guidance.

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