pcb_get_tracks

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

The annotations already declare readOnlyHint and idempotentHint, covering the safety profile. However, the description adds no behavioral context beyond that—no mention of pagination, filtering behavior, or scope of results. It is a minimal statement that does not enrich the agent's understanding of tool behavior.

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, clear sentence with no wasted words. It is front-loaded and easy to parse. This is an example of appropriate conciseness, even if more context could be added elsewhere.

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 there are 4 parameters with no descriptions and an output schema, the description is overly terse. It does not mention pagination, filtering options, or what 'tracks' includes. While the output schema exists and covers return values, the lack of usage context and parameter explanation leaves the agent under-informed for a tool with multiple optional arguments.

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?

Schema description coverage is 0%, and the description provides no parameter semantics. The schema's property names (page, page_size, filter_net, filter_layer) give some hints, but the description does not explain their meaning, defaults, or how they affect results. The description completely fails to compensate for the lack of schema documentation.

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 'List board tracks.' uses a specific verb (List) and resource (board tracks), clearly distinguishing it from sibling tools like pcb_get_nets or pcb_get_zones. It is immediately obvious what this tool does without ambiguity.

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?

There is no guidance about when to use this tool versus alternatives. It does not mention scenarios, prerequisites, or exclusions. The description is purely functional and leaves the agent without direction on selecting this over other tools.

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