list_profiles

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

No annotations are provided, so the description must disclose behavioral traits. It states the return format (names with source) but does not explicitly mention that the operation is read-only or has no side effects. While 'list' implies a query, explicit confirmation would improve transparency.

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 concise and well-structured: first sentence states purpose, second explains parameters, third describes return format. No fluff, every sentence earns its place.

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?

Given the lack of an output schema, the description adequately covers the return format (names with source). However, it does not mention potential pagination, ordering, or the scope (all presets vs. current context). For a simple list tool, this is mostly sufficient but could be more complete.

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 fully explains both parameters: 'kind' with valid values (machine, process, filament, None) and 'search' as a case-insensitive substring filter. This adds significant meaning beyond the 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?

The description clearly states the tool's purpose: 'List OrcaSlicer presets.' It specifies the verb 'list' and the resource 'presets,' and distinguishes from sibling tools like 'get_profile' (single profile) and 'update_profile' (modification) by focusing on listing.

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 explains how to use the parameters (kind and search) but does not explicitly provide when-to-use or when-not-to-use guidance compared to siblings. For example, it lacks a note like 'use get_profile for detailed information on a specific preset.' However, the parameter explanation is clear and contextually helpful.

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