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

Annotations show destructiveHint=false and readOnlyHint=false, confirming it's a non-destructive write operation. The description explains what the tool creates and sets, though it does not elaborate on authorization or side effects beyond creation.

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 (two sentences) and front-loaded with the primary action. However, the inclusion of 'description' and 'pinned starter message' without schema support adds unnecessary ambiguity.

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 covers the main purpose and output (returns conversation ID) but lacks context on prerequisites (e.g., needing a template) and error cases. The schema descriptions partly compensate, but the mismatch between described behavior and parameters reduces completeness.

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 100% but the description mentions setting 'description' and 'pinned starter message' which are not present as parameters. This could mislead agents into thinking these are configurable via the tool, when they are likely template-defined.

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 group from a pre-configured template' and enumerates the actions (sets title, description, optionally pinned message, invites members, returns conversation ID), distinguishing it from siblings like colony_create_group_conversation.

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 does not explicitly state when to use this tool versus alternatives (e.g., colony_create_group_conversation). The parameter description for template references colony_list_group_templates, implying prerequisite knowledge, but usage guidance is implicit.

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