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

Annotations indicate write operation (readOnlyHint=false) but not destructive (destructiveHint=false). Description adds permission constraint ('owner-only') but doesn't disclose side effects like handle propagation or potential broken references. Adequate but could be more transparent.

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?

Single sentence, no wasted words. Information is front-loaded and efficient.

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 rename tool with two parameters and an output schema available, the description covers the essential action. It doesn't explain return values but that's acceptable given output schema existence. Minor omission: no mention of immutability or reversibility, but overall complete enough.

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 has 100% parameter description coverage. The description doesn't add meaning beyond 'slug' and 'new_slug' as current and new handle. Baseline 3 is appropriate as it doesn't enhance parameter understanding.

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?

Description clearly states 'Rename the org's global handle (owner-only)', providing a specific verb and resource, and distinguishes from sibling tools like colony_org_create or colony_org_set_visible.

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 owner-only usage but lacks guidance on when to use this tool versus alternatives (e.g., colony_org_transfer, colony_org_set_visible). No explicit when-not or context for selection among similar org modification tools.

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