constraints-set

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that it 'sets' a property, implying mutation, but does not describe side effects, error behavior, or any additional context such as whether it is destructive or requires specific permissions.

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 a single sentence, which is concise and front-loaded with the verb. However, it is so minimal that it borders on under-specification rather than true conciseness—it is appropriately short but lacks essential detail for a tool with six parameters.

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 tool's complexity (six parameters), the absence of an output schema, and no annotations, the description is far too minimal. It does not explain parameter interactions, error handling, or provide enough context to safely invoke the tool, making it incomplete for practical use.

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 does not explain any of the six parameters. The schema titles provide minimal hints (e.g., 'New value as JSON'), but with 0% schema description coverage, the description should compensate. It adds no parameter meaning beyond what the raw schema already implies, leaving users to guess the exact format and usage.

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 uses the specific verb 'Set' and identifies the resource as an RNA property on an object or pose-bone constraint. This clearly distinguishes it from sibling tools like constraints-list, constraints-add, and constraints-remove, making the purpose unambiguous.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The description simply states what it does without context on when to apply it, which is insufficient for a setter tool with many siblings.

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