Inspect SOLIDWORKS drawings for dimensions, views, and annotations. Check drafting standards and generate a detailed report.
Handle analyze drawing comprehensive.
| Name | Required | Description | Default |
|---|---|---|---|
| input_data | Yes | The input data value. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose behavioral traits such as read/write nature, side effects, authentication needs, or performance impact. The analysis likely reads data, but this is not confirmed.
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 vague sentence that does not earn its place; it adds no information beyond the name. True conciseness should provide meaningful insight in minimal words.
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 complex nested input schema and the large set of sibling analysis tools, the description is severely incomplete. It lacks details on output, use cases, and differentiation from similar tools.
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 100% (all parameters have descriptions in the schema). The tool description adds no value beyond the schema, but per the rubric the baseline is 3 when coverage is high.
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 'Handle analyze drawing comprehensive' is a vague restatement of the tool name. It does not specify a concrete verb or resource, and fails to differentiate from sibling tools like analyze_drawing_dimensions or generate_drawing_report.
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 versus the many similar sibling tools (e.g., analyze_drawing_views, check_drawing_standards). The description does not mention prerequisites, context, or exclusion criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.