get_dimension

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

No annotations are provided, so the description must compensate. It indicates the operation is a read from the active model but does not disclose whether it is destructive, requires specific permissions, or handles errors (e.g., dimension not found). The return format is not described, though an output schema exists.

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 two sentences, front-loaded with the core purpose, and every sentence adds value. No unnecessary words or repetition.

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 simplicity of the tool and the existence of an output schema (not shown), the description covers the basic purpose and applicability. However, it lacks mention of prerequisites (e.g., open model), error handling, or whether it works offline. For a read tool, this is adequate but not comprehensive.

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% with detailed examples for 'name' and 'dimension_name'. The description adds context about dimensions coming from sketches, features, or global dimensions, but this does not significantly enhance understanding beyond the schema. Baseline 3 is appropriate.

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 retrieves a dimension value from the current model, specifying it can be from sketches, features, or global dimensions. It distinguishes implicitly from sibling 'set_dimension' by indicating a read operation, but no explicit differentiation from other getters.

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 mentions 'useful for parametric modeling and design validation', giving context, but does not explicitly state when to use this tool versus alternatives like 'set_dimension' or 'add_dimension'. No exclusions or prerequisites are provided.

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