get_component

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

With no annotations, the description carries the full burden, and it does disclose the return content, including nested pin/net information. However, it does not explicitly state that the operation is read-only or describe permissions, failure behavior, or what all_parameters changes.

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 definition is a single compact sentence with no filler, and the key return content is front-loaded. It is slightly cryptic because the list of returned fields is packed together without structural cues.

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 tool with no annotations, no output schema, and 0% schema description coverage, the description is too thin. It lists some return fields but leaves all input parameters and usage context undocumented.

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 does not explain any of the three parameters. It does not clarify that project and designator identify the component, nor does it explain the all_parameters flag; 'parameters' in the description appears to refer to returned component parameters instead.

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 names a specific resource and enumerates the returned content: component parameters, every pin with its net and other net-connected parts, and PCB placement. That is more precise than a tautology and distinguishes it from search tools, though it does not explicitly name sibling tools like search_components or pcb_placement.

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 explicit guidance about when to use get_component versus search_components, get_bom, or pcb_placement. Usage is only implied by the word 'details,' leaving the agent to infer that this is for fetching a single component's full record.

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