Check components exist

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds that it 'checks existence' but provides no additional behavioral details beyond what the annotations convey. It does not contradict the annotations, so this is not a red flag, but the description itself contributes little extra transparency.

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 concise, using only two sentences to convey the purpose and a usage suggestion. It wastes no words and is well-structured, with the core function stated first and the usage context second.

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 the rich set of sibling tools, the description effectively differentiates this tool as a lightweight existence check. However, it does not mention what the tool returns (e.g., a list of existing vs. missing components or a simple boolean), which could be relevant for an agent deciding whether to call this tool. It also omits potential error conditions like invalid file paths, but these are not critical for correct invocation.

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?

Both parameters (filepath and component_names) have clear descriptions that explain their purpose and format. The schema coverage is 100%, and the descriptions are sufficient for an agent to understand what values to provide. No additional parameter-level details are missing.

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's function: checking if one or more components exist in an Altium library. It uses specific language ('Check if', 'exists') and identifies the resource type (Altium library), which distinguishes it from sibling tools like list_components or get_component that have different purposes.

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 explicitly suggests using this tool to validate component names before operations like rename, copy, or delete, providing clear guidance on when to use it. It does not, however, mention alternatives or specify when not to use it, which would make the guidance more complete.

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