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

Annotations already signal read-only, idempotent, and non-destructive behavior; the description adds useful return semantics by stating that both the dimensions and their concept counts are returned. It does not elaborate on format or sorting, but for a parameterless read-only list this is adequate.

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?

A single well-structured sentence front-loads the action and result, with the dimension names offloaded to a parenthetical list. Every element earns its place without redundancy.

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 simple, parameterless, annotated read-only listing tool, the description fully states what the agent gets: all 15 top-level dimensions plus concept counts. No schema or output-format caveats are required to invoke it correctly.

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 tool has zero parameters and the schema confirms this, so the baseline for a no-parameter tool applies. The description adds no parameter guidance because none is needed.

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 names a specific verb ('List') and resource ('top-level dimensions of the Master Cymetica Ontology'), pins an exact cardinality (15), and enumerates them, making its scope unmistakable. This clearly distinguishes it from sibling ontology tools like browse_ontology, resolve_ontology_concept, and search_ontology.

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 phrase 'List the 15 top-level dimensions' provides clear context for when to call this overview tool instead of browsing or searching a specific concept, but it does not explicitly state exclusions or name alternatives. The intended use is strongly implied rather than explicitly routed.

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