list_namespaces

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

The annotations already indicate read-only and open world behavior. The description adds that it lists namespaces available to the current user, which implies authentication, but does not disclose pagination behavior or other traits beyond annotations.

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?

Two short sentences with no filler. The description is front-loaded with the core purpose and a practical filter example, making it efficient and scannable.

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?

Given the parameter descriptions in schema and the open world hint, the description is mostly complete for a list tool. It lacks details about the response format or pagination behavior, but these are often implicit for list operations.

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?

All parameters are documented in the input schema with descriptions, so the description adds no additional parameter semantics. The filtering hint is a usage guideline, not parameter detail.

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 the tool lists all namespaces available to the current user, specifying the resource (namespaces) and scope (current user). It also provides a filtering example, distinguishing it from other tools like get_namespace.

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 gives explicit filtering guidance for groups but does not specify when to avoid this tool in favor of alternatives like get_namespace for specific namespaces. The context is clear, but exclusions are missing.

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