find_part_and_open_in_creo

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

No annotations are present, so the description bears full responsibility. It only states 'automatically open it in Creo' without disclosing prerequisites (e.g., Creo must be installed and running), side effects, or error behaviors. This is insufficient for an action that launches an external application.

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 concise sentence that directly states the tool's purpose. While brief, it contains no unnecessary words and is easy to parse. Could benefit from more detail, but not at the expense of conciseness.

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 no output schema and a tool that triggers an external application (Creo), the description lacks important context: what happens upon success (e.g., returns confirmation?), failure modes, and whether it blocks until Creo is opened. The simplicity of inputs does not fully compensate for missing behavioral details.

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 coverage is 100% with one parameter 'partNumber' described as 'Part number to find and open'. The description does not add additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 verb 'find' and 'open' with explicit resources: 'a part in Windchill' and 'automatically open it in Creo'. It distinguishes from siblings like 'windchill_search_part' (search only) and 'creo_open_model' (open already found model) by combining both actions.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't clarify when to use 'windchill_search_part' + 'creo_open_model' separately instead. No exclusions or context for appropriate usage are given.

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