Edit Xpresso Port

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

No annotations provided, so description carries full burden. Explains each action's behavior in detail: add uses GvNode.AddPort, connect auto-detects direction, disconnect removes incoming connections, set_value writes default, remove deletes. Discloses key behaviors and constraints.

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?

Single paragraph, front-loaded with purpose, each sentence earns its place. No redundant information; efficiently covers all actions and prerequisites.

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?

With 7 parameters, nested objects, and no output schema, the description covers usage pattern, prerequisite, and action details. Could improve by mentioning error handling or return value, but adequate for the complexity.

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 100%. Description adds significant meaning beyond schema, e.g., explaining auto-direction detection for connect, value coercion for set_value, and clarifying required parameters for each action.

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?

Clearly states it is a low-level Xpresso port primitive covering cases apply_xpresso_graph cannot express. Lists specific actions (add, connect, disconnect, set_value, remove) with explicit verbs, distinguishing it from sibling tools.

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?

Explicitly advises using list_xpresso_nodes first to discover node path ids and existing ports, and mentions it covers cases apply_xpresso_graph cannot express. Provides clear context for when to use, but does not explicitly state when not to use.

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