List board presets

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

With no annotations provided, the description carries full burden for behavioral disclosure. It implies read-only operation by stating 'list built-in board presets derived from existing Quartus projects,' but does not explicitly confirm nondestructive behavior, rate limits, or what happens if no presets exist. Adequate but not detailed.

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 a single sentence of 18 words, front-loaded with the core action ('List built-in board presets'). Every word contributes meaning, with no redundancy or wasted space.

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 simple list tool with one optional parameter and no output schema, the description adequately covers the scope and contents of the output. However, it could be slightly more complete by mentioning that presets are read-only or that the list may be empty if no projects exist.

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 coverage is 100% as the optional 'presetId' parameter is described in the schema. The tool description adds no additional parameter meaning beyond the schema, which is acceptable given high coverage. The description's mention of output contents (device settings, pin resources) is not parameter-related.

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 built-in board presets derived from existing Quartus projects, including default device settings and named pin resources. It uses a specific verb ('List') and resource ('built-in board presets'), and it is distinct from sibling tools that focus on project creation, extraction, or hardware 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 provides no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. It only describes what the tool does, leaving agents without context for optimal selection among sibling tools.

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