get_rig_constraints

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

With no annotations provided, the description carries the full behavioral burden. Calling it 'Get' plus returning 'constraints and rules' reasonably signals a read-only lookup, and it adds useful domain framing ('organic imperfection rules'), but it says nothing about permissions, caching, or failure behavior for an invalid type.

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, front-loaded with the action and scope, then the constraint-relevant enumeration. No filler.

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, so return values needn't be explained, and the description supplies the critical input vocabulary the schema omits. Complete enough for a simple getter; only minor validation details are absent.

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 coverage is 0% and the single rig_type parameter has no documented enum in the schema. The description compensates by enumerating all ten valid values, which is exactly the kind of meaning the schema lacks, though it does not clarify case sensitivity or rejection behavior for other strings.

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?

States a specific verb and resource ('Get the physical constraints and organic imperfection rules for a specific camera rig type'), which is unambiguous on its own. It does not explicitly distinguish itself from analogous siblings such as get_locomotion_constraints or get_skeleton_blueprint, so it falls short of a 5.

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 implies usage via 'for a specific camera rig type', making the intended call context inferable. However, it offers no when-to-use/when-not-to-use guidance and names no 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.