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

Annotations already assert read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context beyond annotations: it requires login, does not read private chat content, does not return contact details, and explains that ended status after a real reply is derived read-only. The final sentence touches on application/cancellation workflow but does not explicitly claim this read tool performs those mutations.

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 the login requirement and read-only scope, but the final sentence about applying, canceling, and declining applications is only loosely relevant to a get tool and may distract from the core 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 read-only status tool with no output schema, the description adequately covers what is returned (status, counterparty, organization) and what is excluded (contact info, private chat). It is less complete on the required conversationId parameter, and the apply/cancel sentence introduces workflow context that is not fully connected to this tool's behavior.

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% for the single required parameter, conversationId, so the schema provides only type and length constraints. The description implies the parameter identifies the caller's own two-person conversation but gives no format, boundary, or selection guidance beyond that implication.

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 read-only action on a specific resource: the assist-contact status, counterparty, and organization for the caller's own two-person conversation. It also clarifies what it does not do (does not read private chat body, does not return contact info), which helps distinguish it from message-reading and contact-exchange siblings, though no sibling is named directly.

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?

Provides login requirement and read-only scope, and mentions related apply/cancel/decline operations, implying this tool is for viewing status rather than mutating it. However, it does not explicitly state when to choose this tool over alternatives such as get_contact_exchange_state or update_quick_contact_request.

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