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

The annotations already establish that this is a safe, read-only, idempotent, non-destructive operation. The description adds useful scope and return-content information by stating that it returns the 16 top-level dimensions and their concept counts, but it does not describe ordering, output format details, or other behavioral traits beyond the annotations.

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 a single front-loaded sentence with no filler, and the enumeration earns its place by telling the agent what dimensions are included. The parenthetical list is dense but directly relevant to the tool's purpose.

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 zero-parameter read-only list tool with rich annotations and no output schema, the description is largely complete: it states what is listed and that concept counts are included. It could be stronger only by clarifying its relationship to the ontology-related sibling tools.

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?

This tool has zero parameters, so there are no parameter semantics to explain. The baseline score of 4 applies because the schema is empty and the description does not need to compensate for undocumented parameters.

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 gives a specific verb and resource: 'List the 16 top-level dimensions of the Master Cymetica Ontology' and even enumerates the dimensions. It is clear what the tool does, but it does not explicitly distinguish itself from related siblings such as browse_ontology, search_ontology, or resolve_ontology_concept.

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 implies that this tool provides a top-level ontology overview, but it gives no explicit when-to-use guidance. It also does not mention when to choose browse_ontology, search_ontology, or resolve_ontology_concept instead.

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