create_full_port

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

No annotations are provided, so the description carries the full burden. It only states the action without disclosing side effects, mutation implications, or requirements like whether parent_id must reference an existing block. This is insufficient for a model-mutating operation.

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 concise sentence, which is appropriately front-loaded with the core purpose. However, it is under-specified to the point of being unhelpful; conciseness is achieved at the expense of essential information.

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 creation tool with two required parameters and an output schema, the description should at least clarify the role of each parameter and any contextual constraints. It does none of this, leaving the agent to guess about the parent block relationship and return behavior.

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%, and the description provides no explanation of 'name' or 'parent_id'. An agent cannot infer that parent_id is the block's identifier or what naming constraints apply. The description adds zero value beyond the schema field names.

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 verb (Create), the resource (SysML FullPort), and the target (a Block). It distinguishes from other port creation tools by naming the specific port type, though it doesn't explicitly contrast with create_proxy_port or create_flow_port.

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?

No guidance on when to use this tool versus the many sibling creation tools. It doesn't mention alternatives, prerequisites (e.g., parent block must exist), or any exclusions. The agent is left to infer when a FullPort is appropriate.

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