robot_reason

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

No annotations provided. The description explains that it runs a reasoner and controls inferred axioms via axiom_generators, but does not disclose whether the input ontology is modified, permissions needed, or potential side effects. Some behavioral traits are covered, but gaps remain.

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 two paragraphs with a clear first sentence and a list. It is concise, but the list of reasoners could be more structured. Still, it is brief and front-loaded.

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?

Despite having 21 parameters and no schema descriptions, the description only addresses two. It lacks details on input/output handling, ontology creation flags, and other common options. Output schema exists but is not mentioned.

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?

Schema description coverage is 0%. The description only explains 'reasoner' (with options) and 'axiom_generators' (with example). The remaining 19 parameters receive no explanation, leaving the agent uncertain about input, output, paths, flags, etc.

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 runs an OWL reasoner to classify and check consistency. The verb 'run' and resource 'OWL reasoner' are specific, and the purpose is distinct from sibling tools like robot_annotate or robot_merge.

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 reasoning tasks but does not specify when to use it over alternatives like robot_materialize or robot_classify. No explicit guidance on prerequisites or exclusions.

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