Get component pins

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

Annotations indicate readOnlyHint and idempotentHint. The description adds critical context: pinType is unreliable and should be treated as weak hint, which is beyond the annotations and helps avoid misinterpretation.

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 two sentences: first states the core function, second adds a crucial caveat. Every sentence is value-adding and there is no fluff.

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 an output schema exists, the description sufficiently states what data is returned (pin numbers, names, coordinates, pinType) and the reliability caveat. No additional context is needed for this simple 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 only parameter 'primitiveId' has no schema description (0% coverage). The description minimally says 'by its primitive ID' which adds little beyond the parameter name. For a simple string parameter, the gap is small but not compensated.

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 retrieves exact pin numbers, names, coordinates, and pinType for a schematic component by primitive ID. It uses specific verbs and resource, and the sibling list shows no other tool covers pins, so it is well-differentiated.

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 specifies the tool is for getting pin details when you have a primitive ID, and includes a caveat about pinType reliability. It does not explicitly state when not to use, but the clear purpose and warning provide good guidance.

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