List presets

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

Beyond the readOnlyHint annotation, the description reveals key behavioral traits: default filtering to user presets plus the selected preset, the 'noise' of ~400 system presets, and the hidden_system counter for filtered entries. This gives the agent significant insight into expected behavior and output.

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 and well-structured: first sentence states the purpose, second explains default behavior and parameter usage, third describes the hidden_system output. No unnecessary words or repetition.

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 only two optional parameters, a readOnlyHint annotation, and no output schema, the description covers the essential contextual information: default filtering, parameter effects, and a key return field (hidden_system). It is sufficient for an agent to invoke the tool correctly.

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 input schema has no parameter descriptions (0% coverage), but the description fully explains both parameters: include_system=True for the full list, and type='print'|'filament'|'printer' to restrict to a category. It also clarifies the default behavior associated with leaving parameters unset.

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 lists print/filament/printer presets with flags for system/selected/visible. This specific verb+resource+scope differentiates it from sibling preset tools like save_preset, delete_preset, and select_preset.

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 provides clear context on when to use the tool (listing presets) and how to adjust behavior via include_system and type parameters. However, it does not explicitly name alternative tools for exclusions or when-not-to-use scenarios, so it misses the 'alternatives' criterion for a 5.

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