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

Annotations have no additional hints beyond non-read-only and non-destructive. The description reveals it creates a version and requires access checks, but lacks detail on the effect on other resources or the creation process.

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 with three sentences: first states purpose, the rest provide critical usage guidelines. No unnecessary words, and key information is front-loaded.

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?

The description lacks explanation of what a template version is, the relationship between chatId and version, and the output. It focuses heavily on access control but omits essential semantics for a tool with an undocumented schema.

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 the description does not explain any of the three parameters (communityId, chatId, version). The agent gets no help on what values to provide.

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 'Create a new AI Cofounder template version,' which is a specific verb+resource. It distinguishes from siblings like get_ai_cofounder_template_version and update_ai_cofounder_template by its creation action.

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 guidance: check business permissions, FREE businesses cannot use, call check_business_tool_access, show grace-period warning, and never proceed when blocked. This clearly tells when and how to use the tool.

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