Transform simulation data into an inference or hypothesis, excluding reserved epistemic kinds to produce valid results.
Turn a simulation into an inference|hypothesis (reserved kinds rejected).
| Name | Required | Description | Default |
|---|---|---|---|
| content | No | ||
| subject | No | ||
| sessionId | No | ||
| simulationRef | No | ||
| targetEpistemicKind | No |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits itself. It communicates a transformation and a rejection rule, but does not explain side effects, persistence, whether the simulation is mutated or consumed, required context, or failure behavior.
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 single sentence is short and free of fluff, but it is under-specified rather than concise. For a tool with five undocumented parameters and no annotations, this brevity is a deficiency, not a strength.
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?
There is no output schema, no annotations, no parameter guidance, and no usage context. The description is far too incomplete for an agent to reliably select and invoke this tool among 39 siblings.
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% and all five parameters are bare strings. The description mentions no parameter names or meanings, so it does nothing to help an agent populate content, subject, sessionId, simulationRef, or targetEpistemicKind correctly.
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 states a specific operation: turning a simulation into an inference or hypothesis, and adds a constraint that reserved kinds are rejected. This distinguishes it from siblings like simulate or propose, though 'inference|hypothesis' remains somewhat domain-specific and underspecified.
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?
No explicit guidance is given about when to use materialize versus siblings such as propose, confirm, commit, or simulate. The reserved-kinds rejection hints at a boundary, but no alternatives or selection conditions are described.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.