Select Controller

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

The description adds significant behavioral context beyond annotations: it states that connecting disconnects any previous controller and makes the new controller's tools available. This aligns with the idempotentHint and openWorldHint annotations without contradiction.

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?

Two sentences front-load the core action and immediately explain the consequence. Every word is necessary; no extraneous detail.

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?

The description covers the tool's function, side effects (disconnect old, make new tools available), and outcome. It lacks mention of error handling (e.g., invalid name) or return value, but these are minor gaps for a simple selection tool with no output schema.

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 single parameter 'name' is already well-documented in the input schema (coverage 100%). The tool description adds no additional semantic meaning for the parameter beyond what the schema provides, meeting the baseline expectation.

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 the specific verb 'connects' and resource 'nomos controller by name', clearly stating the action. It distinguishes itself from siblings like 'add_controller' or 'list_controllers' by focusing on activating an existing controller definition.

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 explains the effect (tools become available), which implies when to use it (after listing controllers). However, it does not explicitly mention prerequisites or alternatives like 'use list_controllers first to get valid names'.

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