eda_pcb_primitive_dimension_get_all

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only restates the method signature and return type, offering no statement on side effects, permissions, or behavior when optional parameters are omitted. The 'getAll' name implies read-only, but that is not explicitly disclosed.

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 short and front-loaded with the signature, followed by a brief Chinese summary. It avoids fluff, though the English method name and Chinese translation are somewhat redundant.

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 get-all tool with no annotations and no output schema, the description is incomplete. It does not explain the optional parameters' semantics, does not state whether all dimensions are returned by default, and gives no usage context or example. An agent would need external knowledge to use the optional parameters correctly.

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 description adds the function signature showing layer?: TPCB_LayersOfDimension and primitiveLock?: boolean, which is meaningful because the schema's args array is opaque. However, it does not explain what these parameters mean or how they affect results. The schema already documents the generic args and windowId shapes, so this partial addition deserves a middle 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 states a clear verb-resource pair: '获取所有尺寸标注' (get all dimension annotations), and the signature pcb_PrimitiveDimension.getAll reinforces this. It is distinct from sibling tools like eda_pcb_primitive_dimension_get or eda_pcb_primitive_dimension_get_all_primitive_id by implying full objects, but it does not explicitly differentiate itself.

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 such as getting a single dimension or getting only primitive IDs. It does not mention filtering by layer or primitiveLock, nor any conditions under which the optional arguments should be supplied.

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