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

With no annotations, the description carries the full burden. It discloses a useful constraint (the 3-character code must be unique in the target namespace) and a side effect (the board URL will change), which is real behavioral value. But it omits auth/permission requirements, reversibility, and failure behavior on code collision.

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?

Four short sentences, front-loaded with purpose and each contributing something (purpose, constraint, side effect, usage). No filler, though it is slightly more verbose than a single tight sentence would be.

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 mutation tool with no annotations and no output schema, the description covers purpose, a uniqueness constraint, a side effect, and a use case, which is reasonably complete. It still leaves gaps around permissions and what happens to related board data or on collision failure.

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 description coverage is 100%, and namespace_slug's schema already points to list_namespaces for discovery. The description adds no syntax, format, or constraint detail for the two parameters beyond what the schema provides, so baseline 3 is correct.

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 (move) and resource (board) with explicit scope: 'from its current namespace to a target namespace'. This is clearly distinguishable from siblings like transfer_board_ownership (ownership) and move_task (tasks), without needing to open a 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?

Provides a clear use case: 'Use this to consolidate boards into an organization namespace.' This gives an agent solid context for when to reach for it. However, it doesn't name alternative tools (e.g., transfer_board_ownership) or state when NOT to use it.

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