windchill_get_part

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

No annotations are provided, so the description bears full responsibility. It states 'Get detailed part information' but does not disclose any behavioral traits (e.g., read-only, authentication needs, response format, or side effects). The description is too sparse to be transparent.

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 sentence, concise and to the point. Every word is necessary, and it is efficiently front-loaded.

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 simple input (one parameter) and lack of output schema, the description is minimal. It does not explain what 'detailed part information' includes, nor does it address how it differs from similar sibling tools. More context would be helpful 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?

Schema coverage is 100% (the 'number' parameter is described as 'Part number'). The description adds no additional meaning beyond what the schema already provides. Baseline 3 applies because the schema suffices.

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 uses a specific verb 'Get' and resource 'detailed part information from Windchill', clearly indicating it retrieves part details. It distinguishes from siblings like 'windchill_search_part' (search) or 'windchill_get_bom' (BOM), but could be more explicit about what 'detailed' means.

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 on when to use this tool vs alternatives. Sibling tools like 'windchill_get_bom', 'windchill_get_docs', and 'windchill_search_part' serve related purposes, but the description does not clarify when to choose this one.

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