Attach to a running profile

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

Annotations already indicate non-read-only (readOnlyHint=false) and open-world (openWorldHint=true). The description adds useful context about attaching vs. starting and the origin of port/wsEndpoint, but does not disclose failure behavior, error cases, or what happens if the profile is not running. No contradiction with annotations.

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?

Three sentences, front-loaded with the core purpose, each sentence earning its place. No unnecessary detail or repetition.

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?

The description covers purpose and usage well, but since it involves side effects (openWorld) and there is no output schema, it doesn't describe return values or error conditions. For a connection tool, this is a notable gap, though the broader tool suite context partially compensates.

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%, so all parameters are documented. The tool description reinforces that port and wsEndpoint come from the start response and explains the start parameter's effect, adding some value beyond the schema. Baseline 3 is appropriate since the schema already carries the load.

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 attaches the automation client to a running profile, using a specific verb+resource. It distinguishes itself from start_profile by noting this is usually unnecessary and providing a concrete use case (profiles started outside the server).

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?

Explicitly states when to use: 'Use this when the profile was started outside this server' and notes the alternative that start_profile records the endpoint. Also explains the optional start:true to start the profile itself, providing clear context and alternatives.

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