inspect

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

No annotations are provided, so the description carries the full behavioral burden. 'Snapshot' and 'diagnostic queries' imply a read-only inspection scoped to the active part, but the definition does not explicitly confirm no mutation, permissions/auth needs, behavior with no active part, or other side effects.

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 sentences with no wasted text: the first front-loads the scope and returned diagnostic fields, and the second justifies the value over multiple calls. It is appropriately sized for the tool.

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?

An output schema exists and the parameter schema is fully described, so the description need not explain return values or instance selection. It covers the snapshot contents and active-part scope adequately for a read-only diagnostic tool, though it leaves some behavioral and usage-routing details implicit.

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 single parameter 'instance' has complete schema documentation explaining connected Inventor selection and the empty-default behavior. The description adds no further parameter guidance, so this sits at the baseline 3 for 100% schema description coverage.

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?

It states a specific operation and resource: a compact snapshot of the active part with enumerated contents (volume, bbox, counts, feature tree, sketches, thickness). The phrase 'one call instead of several diagnostic queries' hints at aggregation, but it does not explicitly name the sibling diagnostic tools it replaces.

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 a clear use case as a one-call diagnostic overview, implying it should be used instead of several separate queries. However, it does not state when not to use it, prerequisites such as an active part/document, or name specific alternatives among the many sibling tools.

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