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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), so 'Read-only' mostly restates them. The valuable addition is the non-obvious lifecycle rule that 'a reply in the chat also accepts it', which tells an agent the list can change state without an explicit accept call. Pagination behavior is left to the schema, which is acceptable given limit/cursor are documented there.

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, front-loaded with the resource definition, then the acceptance rule, then the safety tag. No wasted words and nothing buried.

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 paginated read-only listing with annotations and a partially documented schema, the description covers what the objects are and the key state transition. It could still state that results are paginated and that account_id scopes the listing, but nothing essential to a correct call 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 67%: limit and cursor are well described in the schema, but account_id carries only a uuid format with no explanation. The description says nothing about any parameter, so it neither compensates for the undocumented account_id nor adds syntax detail beyond the schema. Baseline 3 applies.

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 defines the resource precisely — 'conversations started by people the account does not follow, waiting to be accepted' — which is far more informative than the bare name. It stops short of differentiating from lookalike siblings such as list_follow_requests or list_messaging_chats, so an agent must still rely on the title to confirm this is a listing operation.

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?

Usage is implied by the definition of the resource: use this when you need pending inbound requests from non-followed accounts. There is no explicit when-to-use/when-not-to-use framing and no named alternative for adjacent needs (e.g. accepted/new chats), leaving routing to inference.

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