Get System Status

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

With no annotations, the description carries the burden, and it discloses non-obvious behavior: it does not just read version metadata; it actually probes real PNG rendering. It also mentions reporting versions and limits. It is a read-only diagnostic in spirit, though it does not explicitly state that it has no 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 entire description is one tight sentence with three parallel clauses that are front-loaded with the most important actions. Every part adds distinct information and no filler is present.

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?

For a parameterless status probe with an output schema, the description is complete: it states what is checked, that a real render is exercised, and what is reported. The output schema can handle return details, so nothing critical is missing.

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 tool has zero parameters, so the description does not need to document parameter meaning. The baseline of 4 applies.

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 names a specific resource (system/dependency environment) and concrete actions: detect OpenSCAD, probe real PNG rendering, and report versions/limits. None of the sibling tools cover system-level status, so it is clearly distinguishable from project/model operations.

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 intended context is implied: call this to verify the OpenSCAD/rendering environment before relying on it. However, there is no explicit when-to-use or when-not-to-use guidance, nor any naming of alternatives.

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