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

Beyond readOnlyHint=true, the description discloses the login requirement, pagination, re-validation of visibility/blocking/status, and that contact details are omitted. This is meaningful behavioral context, though the exact status semantics and response shape are not detailed.

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 definition is compact and front-loads the login requirement before the core operation. Every clause contributes either purpose, behavioral context, or a sibling distinction.

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 read-only, paginated list tool with no output schema and only readOnlyHint in annotations, the description covers auth, filtering, privacy, and type separation well. It stops short of fully documenting parameter behavior and return/pagination metadata.

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?

With four parameters and 0% schema description coverage, the description must carry more weight. It does imply direction, scenario filtering, and pagination, but it does not explicitly map cursor/activityId/organizationId to their meanings or explain the enum behavior beyond what the schema shows.

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 states a specific verb and resource: paginated query of the user's own communication requests, filtered by direction/scenario. It also distinguishes this from cooperation-plan requests and assistance-contact applications, so the agent can separate it from nearby request 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?

It gives a clear usage context ('查本人交流请求') and explicit exclusions ('与合作方案请求、协助联系申请不同，不混用id'), plus the precondition that login is required. It does not explicitly route the agent between this list tool and single-record tools such as get_connection_request.

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