ray

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

With no annotations and no additional description, the tool's behavior is completely opaque. The description fails to disclose whether this is a read-only operation, whether it modifies state, what output it produces, or any side effects.

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 extremely short, but this is under-specification rather than concise clarity. It provides a single vague phrase with no useful structure, front-loading, or elaboration.

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 an output schema, the description is far too minimal to be useful. It does not explain the context, expected results, relationship to rendering pipelines, or when ray tracing should be invoked instead of other image-related tools.

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?

The input schema already fully describes the two optional parameters (width and height) with 100% coverage, so the schema carries the semantic weight. The description itself adds no parameter information, but the baseline of 3 is appropriate given high schema coverage.

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 'Performs ray-tracing' essentially restates the tool name and provides no concrete detail about what the tool actually does or produces. It does not distinguish this tool from siblings like render, png, or mpng, which also relate to image generation.

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 guidance is given about when to use this tool versus alternatives such as render or png. The description is entirely silent on context, prerequisites, or preferred scenarios, leaving the agent to guess.

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