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

Beyond the readOnlyHint annotation, the description adds meaningful behavior: login is required, only the user's own two-person conversations are in scope, private chat content is not read, contact information is not returned, and ended status after a real reply is read-only derived. It does not cover error behavior or pagination, but it adds solid context for a read-only tool.

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 description is compact and front-loads login and read-only scope. The final clause about applying with a reason and cancelling/declining existing applications is useful context but slightly stretches beyond the get-status operation.

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 simple read-only getter, it documents access requirements, scope, privacy boundaries, what is returned (status, other party, organization), and derived ended status. The main gap is parameter-level detail for conversationId, but overall it is sufficiently complete without an output schema.

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 0% and the sole required parameter, conversationId, is never named or explained in the description. The phrase "本人双人会话" implies the ID refers to the user's own two-person conversation, but format, constraints, and selection guidance remain undocumented.

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 read-only operation: viewing quick-contact assistance status for the user's own two-person conversation, including the other party and organization. It also distinguishes the scope by saying it does not read private chat content or return contact details. It is clear, though it does not explicitly contrast with sibling tools such as get_contact_exchange_state or create_quick_contact_request.

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 provides useful preconditions (login required, only own two-person conversations, read-only, no private message body or contact info). However, it does not explicitly say when to use this tool versus alternatives like get_conversation or get_contact_exchange_state, and the sentence about applying/cancelling belongs to related quick-contact workflows rather than this tool's usage.

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