set_transition_guard

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only implies a mutation (setting a constraint) but does not explain whether the guard replaces an existing one, what happens if the transition does not exist, whether the operation is reversible, or any error conditions. This is a significant gap for a mutation tool.

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 with no waste, but it is under-specified for a tool with two required parameters and zero schema descriptions. It lacks any structure such as usage notes or parameter guidance, making it too minimal to be appropriately sized.

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?

For a mutation tool with no annotations and an output schema (not shown), the description does not address return values, error handling, or prerequisites. It is incomplete for an agent to safely call it without additional context.

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 0%, so the description must compensate by explaining the parameters. It does not mention transition_id or guard_expression at all beyond what the names imply. There is no explanation of the expected format or language of the guard expression (e.g., OCL), which is critical for correct invocation.

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 states a specific verb ('set') and resource ('OpaqueExpression guard constraint on a Transition'), making the core purpose clear. It distinguishes from sibling tools like set_transition_trigger and set_transition_effect by focusing on the guard, though it does not explicitly name those alternatives. The term 'OpaqueExpression' may be domain-specific but is sufficient for an agent familiar with UML/SysML.

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. It does not mention that it is for setting guards as opposed to triggers or effects, nor does it provide any conditions, prerequisites, or exclusions. The agent is left to infer usage solely from the tool name.

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