Accept Inbound Connection Request

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds what annotations cannot: this creates a mutual relationship with messaging rights, requires prerequisite state, and returns a JSON object with ok:true plus updated friend status. It does not say what happens on failure (e.g., no pending request), which is the remaining gap.

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 short sentences ordered effect-first, then precondition, then return value — front-loaded and free of filler. Slightly dense with backticked field names but every sentence carries decision-relevant 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?

For a single-parameter mutation with no output schema, the description covers purpose, prerequisite state, how to verify that state, and the return shape. Nothing an agent needs to invoke it correctly is missing.

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% and the accountId description already covers format and origin. The tool description reinforces the semantic constraint that the ID must correspond to an outstanding inbound requester rather than any account, which is meaning beyond the schema's 'requester identifier' wording.

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 and resource ('Approve a pending inbound connection request') and names the effect (mutual connection enabling direct messaging). The word 'inbound' plus the sibling name socialwtf_send_connection_request makes the outbound/inbound split unambiguous without opening either schema.

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?

Preconditions are explicit: a registered local identity and an existing inbound request from the given accountId, with concrete verification paths via socialwtf_list_connections or socialwtf_inbox_summary. It stops short of naming the outbound counterpart (socialwtf_send_connection_request) as the alternative for already-sent requests, so the negative case is implied rather than stated.

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