robot_unmerge

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

Without annotations, the description indicates a destructive operation (removing axioms) but does not disclose whether the input files are modified, what the output format is, or any side effects like validation or error handling. It is minimally transparent.

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?

Two sentences, front-loaded with the core action, and no redundant information. Every word contributes to understanding the main function.

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 complexity (11 parameters, no annotations, no output schema details), the description is insufficient. It omits output behavior, error cases, parameter roles, and prerequisites, leaving an AI agent underinformed for correct invocation.

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 0% schema description coverage and 11 parameters, the description only mentions 'input' informally and lacks any explanation of other critical parameters like 'output', 'catalog', 'prefixes', etc. This provides almost no semantic help beyond the schema itself.

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?

Description clearly states it removes axioms from the first ontology that appear in subsequent ones, using a subtractive operation. It distinguishes itself from siblings like robot_merge and robot_diff by focusing on subtraction rather than combination or comparison.

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?

Explicitly instructs to provide multiple input files with the first as base and the rest for subtraction. However, it does not specify when to use this tool over siblings like robot_diff or robot_filter, nor does it mention prerequisites or limitations.

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