Select preset

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the description does not need to repeat that. It adds the M4a requirement, which is extra behavioral context. However, it does not explain the side effects of selecting a preset or what happens after selection, which would be valuable given the write-like nature.

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 exceptionally concise: one sentence plus a type mapping and a prerequisite. Every word earns its place, and the key information is front-loaded. No unnecessary elaboration.

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?

With no output schema and minimal annotations, the description should provide more context about the tool's behavior, such as what happens when a preset is selected or how it interacts with other operations. While it covers the basics, it leaves gaps in understanding the full scope of the operation.

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 schema has 0% description coverage, but the description compensates by specifying the valid values for 'type' (print|filament|printer). It also clarifies 'name' as a named preset, though it adds no additional format or constraints beyond the obvious. This partial compensation warrants a mid-range score.

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 'Select a named preset', which is a specific verb and resource. It further clarifies the type parameter as print, filament, or printer, making the purpose distinct from sibling tools like list_presets, save_preset, or delete_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 a clear context for what the tool does and includes a prerequisite ('needs M4a'), but it does not explicitly mention when to use this tool over alternatives or list any exclusions. The usage context is implied rather than explicitly stated.

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