list_presets

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

With no annotations provided, the description carries the behavioral disclosure burden. It adds meaningful behavior beyond the schema: default scope is user presets, built-in vendor profiles are searched by substring when `contains` is provided. This helps the agent understand result selection, though pagination and exact return format are not mentioned.

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 compact, front-loads the core action, and every sentence adds necessary information. There is no filler or redundant restatement of the schema.

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 list operation with only two parameters and no output schema, the description covers the essential selection behavior and distinguishes default vs vendor search. It is slightly light on return value details and possible filtering edge cases, but it is adequate for correct tool invocation.

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 description coverage is 0%, so the description must compensate. It explains both parameters usefully: preset_type is constrained to three valid values, and `contains` is a substring filter over vendor profiles. This is sufficient for basic invocation.

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 uses a specific verb and resource ('List OrcaSlicer presets') and clearly enumerates the valid preset_type values. It is easily distinguishable from sibling tools like get_preset and get_current_presets.

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 description gives clear context: by default it returns the user's own presets, and passing `contains` searches built-in vendor profiles by substring. It does not explicitly name sibling alternatives or state when not to use this tool, but the usage context is clear enough for an agent to decide.

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