admin_clear_namespace

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

No annotations are provided, so the description carries full burden. It warns about destructiveness, admin-only, and irreversibility, and describes the return value. This is adequate, though additional details (e.g., behavior on missing namespace) could improve transparency.

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 with a clear header, warning symbols, and structured Args/Returns sections. No unnecessary content, though the formatting could be slightly more compact.

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 two-parameter admin tool with no annotations, the description covers purpose, parameters, return value, and critical warnings. It lacks some details like error handling or concurrency, but is largely complete for its complexity.

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 0%, but the description includes an 'Args:' section that explains both parameters: namespace with an example ('user:alice'), and include_children with its default. This adds meaning beyond the schema's type and default values.

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 'Clear all references in a namespace.' The verb 'clear' and resource 'references in a namespace' are specific. It distinguishes from sibling tools like admin_delete_reference (delete single) and admin_list_references (list).

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 includes warnings about admin-only and destructive nature but provides no explicit guidance on when to use this tool versus alternatives like admin_delete_reference. Usage context is implied but not clearly articulated.

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