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

Annotations already cover readOnly/non-destructive/no open-world, so the remaining burden is low. The description still adds a meaningful trait the annotations don't: results are metadata only, no bodies. It omits any note on result volume, ordering, or pagination, which matters for a parameterless listing tool.

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?

Three short sentences, front-loaded with the core action and scope, then usage, then the follow-up path. No redundant restatement of the title or annotations.

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?

With no output schema, the description does the most important work by stating that only metadata is returned and pointing at get_concept/get_context for bodies. It stops short of describing what metadata fields come back or how large an unfiltered listing may be.

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 100%, so the baseline is 3. The description adds real nuance beyond the schema by stressing that all filters are optional and that 'tag' accepts only a single tag, which clarifies the filtering semantics.

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 and resource ('Enumerate concept metadata') and immediately bounds the scope with '(no bodies)'. The phrase 'when search vocabulary isn't matching' implicitly contrasts it with the search_concepts sibling, so an agent can distinguish listing from searching.

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?

Gives three concrete activation scenarios: orientation in an unfamiliar vault, auditing existing artifacts (e.g. all decisions for a product), and failed search matches. It also routes follow-up for content to get_concept/get_context, though it never explicitly says when to prefer search_concepts instead.

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