get_board_stackup

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

The description implies a read operation by describing the output, but does not explicitly state it is read-only, nor does it disclose any permissions, side effects, or limits. With no annotations, a minimally adequate description is provided.

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?

A single sentence that directly conveys the purpose. No extraneous words, front-loaded with key information.

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 no output schema and no annotations, the description only explains the output. The input parameter is left undefined, making the tool incomplete for correct invocation. For a simple tool, more context is needed.

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 sole parameter 'project' is not described in the description. Schema description coverage is 0%, and the description adds no meaning beyond the parameter name. The agent receives no guidance on how to specify the project.

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 explicitly states the tool returns the ordered physical stackup including dielectric and copper layers with thickness. It uses specific nouns and clearly distinguishes from sibling tools like get_board_info (general info) and board manipulation tools.

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?

No guidance on when to use this tool versus alternatives. The description does not provide context about prerequisites, or when not to use it. Given sibling tools that also read board data, explicit usage cues are missing.

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