List parts

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

The annotation readOnlyHint=true already covers the safety profile, so the description does not need to restate that the operation is read-only. The description adds the useful behavioral detail that the result contains part ids intended for export and assembly insertion. However, it does not mention ordering, configurability, or whether the listing reflects a specific configuration state, which would add further 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 one compact sentence with no filler. It front-loads the core meaning and then adds the most important downstream use of the returned data. It could be slightly more direct by starting with 'Lists' instead of 'The parts', but overall it is efficiently written.

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 simple read-only listing tool with fully documented parameters, the description provides enough context: it names the subject, the source, and the intended downstream use of the returned part ids. There is no output schema, so more detail about the exact return shape would be welcome, but the description is adequate for correct selection and 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?

Schema coverage is 100%, and all three parameters (doc, ws, elem) have descriptive explanations linked to URL segments. The description itself adds no parameter-specific semantics, so the baseline of 3 applies because the schema already carries the burden.

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 identifies the resource (parts) and the producing context (a Part Studio), and it specifies the key content (part ids) for export and assembly insertion. The title 'List parts' supplies the verb, so an agent can infer the action even though the description is a noun phrase. It is distinguishable from sibling tools like get_features or get_elements, though it does not explicitly name them.

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 gives clear context for when this tool is useful: when a caller needs the parts a Part Studio produces, particularly their part ids for downstream export or assembly insertion. It does not explicitly list exclusions or alternative tools that might be preferable in other cases, but the use case is clear and unambiguous.

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