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

With no annotations, the description must convey behavioral traits. It clearly implies a read-only listing operation, but it does not define what 'baseline' means, whether results are sorted, or what the output structure looks like. The output schema is available, which mitigates some ambiguity, but the description itself adds little beyond the basic action.

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 that states the action and scope without unnecessary words or repetition. It is appropriately sized for a simple list-all tool.

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 zero-parameter schema and presence of an output schema, the description is largely complete for a simple listing operation. It could be slightly enriched by noting when to use this vs. inspect_ontology, but that gap is minor and the core purpose is clear.

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 covers 100% of the (non-existent) parameters. The description correctly avoids inventing parameter details. Baseline of 4 is appropriate for a parameterless tool.

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 uses a specific verb ('List') and identifies the exact resource ('all registered baseline ontologies in the catalog'). It clearly distinguishes itself from sibling tools like inspect_ontology (for inspecting a specific ontology) and search_classes/search_properties (for searching inside ontologies).

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 the tool is for enumerating all baseline ontologies, but it does not explicitly state when to prefer this over alternatives, nor does it mention any exclusions or prerequisites. It is minimally viable but lacks explicit guidance on choosing between this and inspect_ontology or search tools.

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