set_default_connector

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

With no annotations, the description carries full responsibility for disclosing behavior. It implies a mutation ('Set') but does not explain the effect on existing defaults, reversibility, or side effects. The qualifier 'copied' adds a constraint but does not clarify why a copy is required or what happens to the original.

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 with no redundant words. It efficiently conveys the core action and the key constraint, earning a top score for conciseness.

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 simplicity (1 parameter, no output schema, no annotations), the description covers the basic action and parameter but lacks sufficient context about the meaning of 'default connector' and the significance of 'copied.' It is adequate but has clear gaps that could confuse an agent.

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 documents 'connectorId' as 'The ID of the connector node to set as default' (100% coverage). The description adds the crucial constraint that the node must be a 'copied' connector node, which is not in the schema, thus providing additional semantic meaning for the parameter.

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 a copied connector node as the default connector.' It uses a specific verb and resource, and the phrase 'default connector' distinguishes it from other set_* tools. However, it does not elaborate on what 'default' means or explicitly differentiate it from potential alternatives.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., must the node be copied first?), context where this is appropriate, or exclusions. The description simply states the function without usage direction.

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