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

Annotations already declare non-read-only, non-destructive, non-idempotent. The description adds the substantive behavioral context the annotations lack: the required permission tier, which wiki policy the list applies under, and the non-obvious effect that a listed non-member gains nothing until they join. It omits response/error behavior, which is partially covered by the output schema.

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?

Front-loads the one-line purpose and then sentences that each carry distinct information (policy semantics, authorization, action requirements, endpoint). Slightly prose-heavy with the nested parenthesis and the trailing API path, but no redundant sentences.

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 4-parameter mutation/list tool with an output schema available, the description covers purpose, authorization, action variants, policy interaction, and the API counterpart. Return-value detail is legitimately left to the output schema; only error/permission-failure behavior is unaddressed.

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%, so baseline is 3, but the description adds real meaning beyond the enum labels: action defaults to list, add/remove require username, and 'username' accepts a username or user ID. It also clarifies the effect of each action on the underlying policy, which the schema does not.

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?

States a specific verb+resource ('Manage a colony's wiki editor list') and immediately frames the scope as the allowlist/karma policy, which cleanly separates it from siblings like colony_edit_wiki_page, colony_lock_wiki_page, and colony_wiki_history. An agent can identify the tool's job without opening the schema.

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?

Gives concrete conditions: it names the three actions with defaults, states that add/remove require a username, and specifies who is authorized (moderator with can_manage_settings, founder, site admin). It does not explicitly exclude or route to a sibling tool, but the policy-based context is a strong when-to-use signal.

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