robot_materialize

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

No annotations are provided, so the description carries the full burden. However, it only says the tool 'materializes inferred superclass relationships using a reasoner' without discussing side effects, permissions, whether it modifies data, or what the output looks like. This leaves significant behavioral ambiguity.

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 concise, consisting of two sentences and a usage note. It front-loads the purpose and is efficient, though it could potentially include more detail without becoming verbose.

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 tool's complexity (14 parameters, no annotations, and a presence in a large sibling set), the description is incomplete. It lacks details on input/output handling, behavior, and safety, leaving an 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 14 parameters, the description only mentions two parameters ('term' and 'term_file') and their purpose. It does not explain the remaining 12 parameters, failing to add meaning beyond the schema's bare structure.

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 that the tool materializes inferred superclass relationships using a reasoner, and explicitly distinguishes it from the sibling tool 'reason' by focusing on asserting existential restrictions. This provides a specific verb and resource (materialize superclass relationships) and differentiates it from similar tools.

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 guidance by advising to use 'term' or 'term_file' to restrict which properties to materialize, and notes the similarity to 'reason' but with a different focus. This gives context for when to use the tool, though it does not explicitly state when not to use it or list alternatives beyond the mention of 'reason'.

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