create_flow_property

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

No annotations are provided, so the description carrries the full disclosure burden. It communicates that the tool creates a FlowProperty and allows three direction values, but it omits prerequisites, parent relationship behavior, and any side effects, which is a 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 one tight sentence plus a short value list. It front-loads the action and adds 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?

Although the tool is simple, the description leaves parent_id semantics unexplained and gives no usage context or alternatives. The output schema might document the return value, but the description still does not set expectations for the parent element or how this fits into SysML modeling.

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 input schema has 0% description coverage, so the description must compensate. It adds meaning to 'direction' by specifying in/out/inout, but it does not explain what parent_id refers to or any constraints on name. Most parameters remain opaque.

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 a specific verb ('Create') and resource ('SysML FlowProperty'), and lists the legal direction values. This differentiates it from nearby siblings like create_flow_port and create_flow_specification by naming the exact element type.

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 explicit when-to-use or when-not-to-use guidance, nor any mention of alternatives. The intended usage is implied by the resource name, but the agent receives no help choosing between this and related flow/element creation tools.

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