fm_config_set_default_connection

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the outcome (set default connection for server start) but does not disclose idempotency, persistence details, error behavior (e.g., if the name doesn't exist), or whether it overrides existing defaults. Minimal transparency beyond the core action.

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?

A single sentence that directly states the tool's purpose. No extraneous words or repetition. Highly efficient.

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 (1 parameter, no output schema), the description is minimally adequate. However, it omits important context such as whether the connection must already exist in configuration and how this interacts with sibling tools like 'fm_config_add_connection'. A complete description would include such prerequisites.

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 100% coverage with one parameter 'name' described as 'Connection name to set as default'. The description adds no additional semantics beyond the schema. Baseline score of 3 is appropriate.

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 action ('Set the default connection') and the context ('when the server starts'). It uses a specific verb-resource pair and distinguishes from sibling tools like 'fm_config_add_connection' (adds a new connection) and 'fm_set_connection' (likely sets the current active connection).

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 does not provide explicit guidance on when to use this tool versus alternatives (e.g., 'fm_set_connection' for temporary changes). It implies usage for persistent default configuration but lacks exclusions or prerequisites such as requiring the connection to already exist via 'fm_config_add_connection'.

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