sql_editor_tab_activate

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the write-without-destruction profile is covered structurally. The description adds one genuinely useful behavioral fact: the setting persists and determines which tab opens next, which the annotations do not convey; it says nothing about failure modes for invalid tab ids.

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 short sentence, front-loaded with the action; the parenthetical earns its place by stating the persistence effect. No padding.

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?

There is no output schema, so return values need no explanation, and the tool is simple. However, adequate coverage would at least point to where a valid tab_id comes from (e.g., sql_editor_tabs), which is missing.

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?

One required parameter at 0% schema description coverage, and the description never explains tab_id — where to obtain it, its format, or whether an unknown id errors. With a single undocumented parameter the description should carry the load and does not.

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 states a specific effect on a specific resource: it sets/remembers the active SQL Editor tab. The parenthetical clarifies the consequence ('the one that opens next time'), which separates it from sibling state readers like sql_editor_state and sql_editor_tabs. Only mild weakness is the informal verb 'remember' for what is a state mutation.

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 when-to-use guidance and no mention of alternatives such as sql_editor_state (to read the active tab) or sql_editor_tab_new/close/reorder. The agent must infer the calling context entirely.

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