pbs_namespaces_list

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

The description labels the operation as 'read-only', which is a key behavioral trait. It also notes that the output includes the `ns` field for hierarchical paths. However, with no annotations provided, the description does not disclose handling of missing stores, error states, or idempotency, leaving some transparency gaps.

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 extremely concise, consisting of two sentences that front-load the core purpose and read-only nature, then detail filtering options and provide an alternative tool. No unnecessary words.

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 presence of an output schema (implied) and moderate parameter count, the description covers the essential aspects: purpose, filtering, and alternative. It is missing a note on prerequisites (e.g., the datastore must exist) and boundaries on recursion depth, but overall it provides sufficient context for an agent.

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?

The description compensates for the low schema documentation coverage (25%) by explaining the key parameters: 'parent namespace' and 'limit recursion depth' (mapping to parent and max_depth). The store parameter is implied as the datastore. This adds meaning beyond the schema, though proximo_target is already described in the schema.

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 'List namespaces within a PBS datastore with optional hierarchical filtering (read-only)', specifying verb (list), resource (namespaces in PBS datastore), and scope (hierarchical filtering). It distinguishes from sibling tools like pbs_namespace_create by explicitly mentioning that tool for adding namespaces.

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 provides explicit guidance by stating 'Use pbs_namespace_create to add namespaces', which tells when not to use this tool. It also implies usage for hierarchical filtering via parent and max_depth. However, it does not elaborate on context when this tool is preferable over other list tools or when to avoid it entirely.

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