solidworks_analyze

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

The description gives no information about side effects or mutability. Despite annotations indicating destructiveHint=true and readOnlyHint=false, the text is silent on whether the tool modifies the document, so the agent is unaware of potential destructive consequences.

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 concise and logically structured, packing essential information about the dispatch mechanism, operation list, and unit conventions into two sentences without redundancy or unnecessary detail.

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?

The description lacks information about return values, output format, or error handling. It also does not clarify the relationship to the dedicated analysis sibling tools, so the agent would not know what to expect from the tool or when its breadth is necessary.

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 description explains the operation discriminator and clarifies that unspecified fields fall back to module defaults and that units follow SI unless a unit field is provided. However, it does not elaborate on individual parameters (e.g., body_name, entity, options), relying on schema titles that lack descriptions.

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 tool as a dispatcher for multiple analysis operations (bounding_box, mass_properties, etc.) and indicates the resource (a SolidWorks document) via the document parameter. It is specific about the actions but does not explicitly state the high-level goal of 'analyzing the active document', slightly reducing clarity.

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 provides no guidance on when to use this tool versus the sibling tools like solidworks_mass_properties or solidworks_inspect. It does not mention typical use cases, preconditions, or scenarios where this dispatcher is preferred, leaving the agent without selection criteria.

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