open-ontologies

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the pipeline sequence (ingest → validate → reason) and mentions it's a convenience wrapper, but doesn't disclose important behavioral traits like error handling (beyond mentioning 'stop on SHACL violations' in the schema), performance characteristics, side effects, or what happens if any step fails. The description adds some context but leaves significant behavioral questions unanswered.

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 extremely concise and well-structured in just two sentences. The first sentence clearly states the purpose and sequence, while the second sentence explicitly names the replaced tools. Every word earns its place with zero wasted text, making it easy for an AI agent to parse and understand quickly.

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 complex 9-parameter pipeline tool with no annotations and no output schema, the description provides good high-level context about what the tool does and when to use it, but lacks details about behavioral characteristics, error handling, performance implications, and what the combined output looks like. Given the complexity and absence of structured behavioral annotations, the description should provide more complete operational context.

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?

With 100% schema description coverage, the schema already documents all 9 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. It mentions the overall pipeline concept but doesn't explain how parameters relate to the three combined operations or provide additional semantic context for any individual parameter.

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 as a 'convenience pipeline' that combines three specific operations (ingest data → validate with SHACL → run OWL reasoning) and explicitly names the sibling tools it replaces (onto_ingest + onto_shacl + onto_reason). This provides a specific verb+resource combination and distinguishes it from all other tools in the sibling list.

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 explicit guidance on when to use this tool versus alternatives: it's positioned as a 'convenience pipeline' that 'combines onto_ingest + onto_shacl + onto_reason, all in one call.' This clearly indicates this tool should be used when the user wants to perform all three operations together rather than calling the individual tools separately.

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