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

Annotations already cover readOnly, idempotent, and non-destructive hints. The description adds meaningful behavioral context beyond that: results are limited to one level (not recursive), the output includes kind and summary, and omitting the path defaults to top-level namespaces. This discloses scope and default behavior the annotations cannot express.

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 sentences with zero waste: the core behavior is front-loaded, the example clarifies, and the usage guidance closes. Every sentence earns its place and there is no redundant filler.

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 read-only, low-complexity tool with no output schema, the description covers the essentials: what is returned (members with kind and summary), the depth limit, the no-path default, and when to use it. Minor gaps remain, such as behavior on invalid paths or how version affects results, but nothing an agent needs to invoke it correctly is missing.

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%, so the parameters are already fully documented. The description's example 'occt.shapes' reinforces the path parameter's meaning but largely duplicates what the schema says ('A namespace path such as occt or occt.shapes'), adding no substantive new semantics. The version parameter is not mentioned in the description at all.

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 states a specific verb and resource: it lists 'the members one level below a namespace path' and gives a concrete example ('occt.shapes'). It also describes the result contents ('each with its kind and summary') and frames itself as a discovery tool distinct from the search/detail siblings.

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?

'Use it to discover what exists before searching for details' is a clear when-to-use directive that positions this tool ahead of the search siblings. However, it does not name the alternative tool explicitly or state a when-not-to-use condition, so it stops short of full exclusion guidance.

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