configure_session

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

No annotations are provided, so the description carries the full burden. It discloses that the tool can view/set defaults and apply auto-promote suggestions, and that using profile launches Chrome with a named profile. However, it does not detail side effects, persistence, or safety aspects (e.g., whether changes affect ongoing interactions).

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 three concise sentences. The first covers the overall purpose, the second explains the two operational modes, and the third provides a critical usage instruction. No redundant information.

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 3 parameters, no output schema, and no annotations, the description explains the main functionality and modes. It notes that viewing returns current defaults and suggestions, but does not specify the return format or how changes affect subsequent session actions. Overall, it is fairly complete but has minor gaps.

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 coverage is 100%, with each parameter described. The description adds extra value beyond the schema by specifying the timing for the profile parameter ('BEFORE any browser interaction'). This enhances the semantic understanding beyond the schema's description.

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 tool can view or set session defaults for recurring parameters like tab and timeout. It distinguishes between viewing current defaults and applying auto-promote suggestions. This is distinct from sibling tools which are mostly browser interaction or evaluation tools.

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 provides clear context for when to use the tool: to view or set defaults, and with the autoPromote parameter to apply suggestions. It also gives a crucial usage tip for the profile parameter (use before browser interaction). However, it does not explicitly state when not to use it or mention alternatives.

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