Perform ray casting from a given origin and direction, returning the hit object, normal, and face index within a specified distance.
从 origin 沿 direction 发射线，返回命中对象/位置/法线/面索引。
| Name | Required | Description | Default |
|---|---|---|---|
| origin | Yes | ||
| distance | No | ||
| direction | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description does not mention side effects, permissions, or any behavioral caveats; it only states the operation.
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?
A single, clear sentence with no unnecessary words.
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?
Does not explain coordinate system, units, no-hit behavior, or return structure beyond listing the outputs.
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?
Only mentions 'origin' and 'direction' in the description, leaving 'distance' unexplained, and provides no details on vector conventions or units.
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?
States a specific verb 'cast' and resource 'ray', clearly indicating it performs a ray cast and returns hit data, distinguishing it from other 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?
Provides no guidance on when to use this over alternatives, nor any context about typical use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.