list_presets

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

With no annotations, the description carries the behavioral disclosure burden. It explains what a preset includes, that explicit connect arguments override presets, and which device families are covered. It does not explicitly state side-effect-free behavior, but 'Show' plus the detailed contents sufficiently indicates a read-only listing.

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 front-loaded with the core purpose and then adds concise supporting detail about preset contents, override behavior, and supported families. Every sentence earns its place, and there is no redundant repetition of the tool name or 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 zero-parameter listing tool with an output schema, the description is complete: it explains what presets are, what settings they supply, how connect interacts with them, and what families are available. No critical context is missing for selecting and invoking this tool.

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 has zero parameters and the schema shows an empty object, so there is no parameter semantics to document. The description instead adds value by explaining what the returned preset data contains and how it relates to connect, which is appropriate for a no-argument tool.

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?

States a specific verb and resource: "Show the device presets `connect(preset=...)` understands, with their settings." The description distinguishes it from other tools by focusing on presets and explicitly relating them to connect. This is unambiguous and not a tautology of the tool name.

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: this tool is meant to reveal what presets connect accepts and what each preset configures. It does not explicitly state when not to use it or name alternatives, but the relationship to connect and the list of families makes the intended use obvious.

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