List Connection Profiles

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering safety and side-effect expectations. The description adds meaningful context by noting that the list includes profiles added during the current session, which is a behavioral detail not derivable from annotations or schema.

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 delivers the core purpose first and appends the only important extra behavior. Every word earns its place, and the structure is immediately scannable for an agent.

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 zero-parameter, read-only list operation, the description provides enough context to invoke it correctly: it lists connection profiles and notes session additions. While there is no output schema, the description does not detail the returned profile fields, but for this simple listing tool that is a minor gap rather than a blocker.

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 tool has zero parameters, so the description is not required to add parameter-level detail. The baseline of 4 is appropriate because there is no parameter surface to clarify.

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?

States a specific verb ('List') and resource ('connection profiles'), and clarifies the purpose is to find profiles to switch to. The phrase 'including any added during this session' adds scope that separates this from a static registry, and the tool is clearly distinct from siblings like current_connection or use_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 communicates a clear usage context: call this when you need to see which connection profiles are available to switch to, including session-created ones. It does not explicitly name alternatives or exclusions, but the simple read-only nature and obvious contrast with siblings like current_connection make the intended use clear.

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