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

With no annotations, the description carries the burden of behavioral disclosure. It clearly specifies the complete output (all classes, datatype properties, object properties in schema-card format), which is the primary behavior. The term 'Inspect' implies read-only, but the description does not explicitly confirm non-destructive behavior or mention any side effects, so it isn't a 5.

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, compact sentence that immediately states the action and outcome. It is front-loaded with the verb 'Inspect' and avoids any unnecessary words 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?

The presence of an output schema reduces the need to explain return values, but the description still lacks essential context: the meaning of the required 'slug' parameter and any guidance on when to use this tool instead of siblings. For a tool with only one parameter and a clearly specified output, the description is decent but not fully complete.

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 input schema defines a required 'slug' parameter with no description (0% schema coverage). The description does not mention 'slug' at all, so the agent has no information about what value to provide. The description fails to compensate for the complete lack of parameter documentation.

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 purpose with a specific verb ('Inspect') and resource ('baseline ontology'), and explicitly lists what it returns (all classes, datatype properties, object properties). This distinguishes it from siblings like list_ontologies (which likely lists available ontologies) and search tools (which filter).

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 provides no guidance on when to use this tool versus alternatives such as search_classes or search_properties. It does not mention any prerequisites or contextual cues, leaving the agent to infer usage solely from the tool name.

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