slicer_info

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

No annotations are supplied, so the description carries the full disclosure burden. It implies a read-only lookup but never states that explicitly, nor does it describe whether the result is paths, version strings, or a status flag, or what happens if OrcaSlicer is not installed.

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 short sentence with no filler, and the key subject (OrcaSlicer plus bundled profiles) is front-loaded. It loses a point only because the fragmentary phrasing costs clarity rather than saving 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?

For a trivial zero-parameter lookup with no output schema, the description gives the gist but not the return shape or the not-found case. It is minimally adequate for such a simple tool, but an agent still cannot predict what it will receive.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies the call is argument-free.

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 sentence indicates the tool surfaces discovery/location information about OrcaSlicer and its bundled profiles, which is a real resource, but it is a verbless fragment ("Where ... were found") rather than a stated action such as "Returns the paths where OrcaSlicer and its profiles were detected." It does partially differentiate from list_profiles, but an agent could easily confuse it with printer_info or get_profile.

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?

There is no guidance on when to call this versus list_profiles or printer_info, and no mention of prerequisites or typical call order. The agent must infer that this is a one-shot environment-discovery call.

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