compile_feature_plan_from_drawing_spec

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

No annotations provided, so the description carries full burden. It discloses that the tool is advisory-only and does not mutate SolidWorks, and that it returns MCP tool names and parameters. Supported archetypes are listed. Missing details on error handling or behavior for unsupported archetypes, but overall strong.

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?

Two short sentences that convey all essential information without redundancy. The first sentence is a clear action statement; the second adds critical behavioral context. No wasted 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?

For a simple tool with one parameter and no output schema, the description covers purpose, non-mutating behavior, and supported archetypes. It hints at output (tool names+params). Minor gap: no mention of error states or behavior when archetype is not supported, but overall sufficient.

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?

The schema has 0% description coverage for its single parameter. The description implies 'drawing_spec_id' is an identifier for a stored DrawingSpec, but adds no additional meaning, format, or usage context beyond the name.

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 compiles a DrawingSpec into a FeaturePlan, uses a specific verb-resource pair, and distinguishes itself by being advisory-only and non-mutating. It also explicitly lists supported archetypes, making its scope clear.

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?

Usage is implied: use when you have a DrawingSpec and want a plan. However, there is no explicit guidance on when to use vs. alternatives (e.g., run_feature_plan), nor any when-not conditions. The advisory nature is mentioned but not contrasted with execution tools.

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