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

With no annotations, the description carries the behavioral burden. It discloses the full scope ('every curated concept'), the optional filter by category, and the discovery-oriented behavior. It does not detail return structure, pagination, or side effects, but for a simple list tool the core behavior is transparent.

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 exactly two sentences, front-loaded with the verb and resource, and includes the key usage guidance. Every word earns its place with no fluff or repetition.

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 simple one-parameter schema and lack of output schema/annotations, the description covers the purpose, scope, and filter sufficiently. It could further describe the exact return shape, but for a concept discovery list the phrase 'lists every curated concept' and 'domain explanations' gives the agent enough context to select and invoke it.

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%; the one parameter 'category' is already well-documented with an enum and description. The tool description only says 'optionally filtered by category,' which adds no additional meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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's action ('Lists') and resource ('every curated concept exposed by get_concept'), while distinguishing it from the sibling get_concept by framing this as the discovery-level counterpart. The optional category filter is also mentioned, giving a precise scope.

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 explicitly says 'Use to discover what domain explanations are available,' which gives a clear when-to-use signal. It does not explicitly mention when not to use it or compare with alternatives, but the tie to get_concept and the discovery purpose is enough context.

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