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

The description adds meaningful behavioral context beyond the annotations: it implies a stateful connection is established and that send_and_wait is gated on successful acceptance. The annotations already indicate a mutation (readOnlyHint=false) but are non-destructive and idempotent, which is consistent with accepting a request. The stateful precondition is useful and not otherwise disclosed.

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?

Two brief sentences convey both the core purpose and the critical enabling condition with no filler. The main action is front-loaded, and the follow-up sentence adds high-value sequencing 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?

The tool is simple (two parameters, one required), has full schema coverage, and includes annotations. The description covers the action and the key precondition for subsequent messaging. A connection accept operation might benefit from stating what happens if no request exists, but this is a minor gap against the low overall complexity.

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 input schema already documents both parameters with 100% coverage: 'handle' is described as the handle that requested connect, and 'token' as an optional alternative to the auth header. The tool description does not add parameter-level detail, so a baseline score of 3 is appropriate.

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 action ('Accept an incoming connect request') with a specific verb and resource. It also distinguishes this from related operations by noting that send_and_wait becomes allowed only after this call, which differentiates it from accept_invite and reject_connect.

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 sequencing context: use this tool before send_and_wait. However, it does not explicitly state when not to use it or contrast it with alternatives like accept_invite, so it stops short of full routing guidance.

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