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

The description discloses that it sets title, description, optionally pinned message, and invites members, which adds context beyond the annotations. Annotations indicate it's a write operation (readOnlyHint: false) and not destructive.

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, front-loaded with the core purpose, and each sentence adds necessary detail without redundancy.

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?

For a simple tool with 3 parameters and an output schema, the description covers the main actions and return value. Minor gap: it doesn't mention that the caller is automatically added (though the parameter description does).

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 schema covers all parameters, but the description adds value by summarizing their collective effect (sets title, description, optionally pinned starter message, invites members). It clarifies the purpose of members and template, and that title_override is optional.

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 it creates a group from a template, specifies the actions (sets title, description, optional pinned message, invites members) and returns the conversation ID. It uses a specific verb and resource, distinguishing it from sibling tools 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 implies usage by stating 'from a pre-configured template' and the template parameter references colony_list_group_templates, but it doesn't explicitly mention alternatives or when not to use this tool.

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