chatgpt_select_profile

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

With no annotations provided, the description carries the full burden. It does disclose the three accepted profile identification types (Folder ID, Display Name, Email), which is useful matching behavior. However, it omits what 'activate' means for subsequent calls, failure behavior on unknown profiles, or whether selection persists across calls.

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, front-loaded sentence that efficiently communicates purpose and key scoping detail without waste. Everything present earns its place.

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?

For a low-complexity tool with one fully-documented parameter and no output schema, the description is nearly complete: it defines the action, scope, and accepted value formats. Minor gaps—such as clarifying that profiles can be enumerated with chatgpt_list_profiles or what happens on invalid input—keep it from a 5.

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?

Schema description coverage is 100% (the 'profile' parameter is fully documented with examples). The description's parenthetical largely mirrors the schema rather than adding new meaning, so the baseline of 3 is appropriate—it neither improves nor degrades parameter understanding.

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?

Clear verb (select) + resource (Chrome profile) + domain context (ChatGPT Web automation). The parenthetical explicitly names the three accepted identification modes, which sharpens the tool's role and distinguishes it from siblings like chatgpt_list_profiles (list vs. select).

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 implies when it's used—before automation, to activate a profile—but never explicitly states context such as 'list available profiles first with chatgpt_list_profiles' or 'select one profile before calling chatgpt_ask'. No exclusions or alternative comparisons are given.

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