render_ldraw_file

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

Discloses rendering to PNG, azimuth stitching, and sample trade-off. With no annotations, description carries full burden; missing details on side effects (overwrites?), output destination (file or return?), and error conditions.

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, no unnecessary words. Front-loaded with purpose, then key behavioral notes.

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?

Covers core functionality for a rendering tool with 4 params, required path. Lacks explanation of output format (PNG returned or saved?), error handling, or file size limits. Moderate completeness.

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 coverage is 0%, so description must add meaning. Explains azimuths as comma-separated degrees and samples effect, but path and resolution (default 640, units?) lack explanation beyond schema.

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?

Clearly states verb (render), resource (LDraw model file with extensions .ldr/.mpd/.dat), and output (PNG image). Distinct from siblings: render_ldraw_text likely renders text, check_renderer is a check tool.

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?

Implies usage by describing parameters (path, samples, azimuths, resolution) and behavior (stitching azimuths, samples vs quality). But lacks explicit guidance on when to use this vs siblings or when not to use.

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