creator_select_node

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains the core behavior (select by UUID) and the special case (omit to clear), which is beyond the schema. However, it does not disclose edge cases such as invalid UUID handling, whether the selection replaces any existing selection, or any side effects beyond changing the selection state.

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 two short, direct sentences with no filler. It front-loads the primary action and immediately covers the exception case, making it highly concise and well-structured.

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 simplicity—one optional parameter, no output schema, no annotations—the description is fully sufficient. It explains the main function and the clearing behavior, leaving no critical gaps for an agent to invoke it correctly.

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 schema already provides a description for the uuid parameter ('Node UUID; omit to clear'), and the tool description essentially repeats this. Since the schema covers 100% of the parameter semantics, the description adds little new meaning, keeping it at the baseline of 3.

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 a specific verb 'select' with the resource 'node' and clearly defines the behavior of omitting the UUID to clear selection. It distinguishes from sibling tools like creator_get_node (retrieval), creator_create_node (creation), and creator_list_nodes (listing), 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?

The description provides clear context for when to use the tool: selecting a node by UUID or clearing the selection by omitting the UUID. However, it does not explicitly state when not to use it or name alternative tools, leaving room for implied usage rather than explicit guidance.

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