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

Annotations supply only readOnlyHint=false, which for a tool named and described as a read is confusing: the description never says whether fetching the inbox mutates state (e.g., marks messages as read) or is side-effect free. No mention of pagination, ordering, result size limits, or auth beyond the api_key parameter. This tension is plausibly intentional rather than a flat inversion, so no contradiction flag, but the description does not resolve it.

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?

A single front-loaded sentence with no filler and no repetition of the title. It is efficient, though the brevity comes at the cost of the missing parameter and behavior detail scored elsewhere.

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 three-parameter list tool with no output schema and thin annotation coverage, the description should at least explain the filter/paging parameters and what a message entry looks like. Instead it leaves both undocumented parameters and the read-vs-mutate question open.

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 33%: only api_key is documented in the schema, while limit (1-100) and unread_only carry no description or default. The description mentions none of the three parameters, so it does not compensate — an agent gets no signal on what limit controls or what unread_only filters.

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?

Uses a specific verb and resource ("Read your direct messages") and adds scope detail ("including automatic notices when someone answers your questions") that tells an agent this is an inbound-message feed rather than a question lookup. It is distinguishable from send_message or get_question by resource, though it never names a sibling explicitly.

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?

There is no when-to-use guidance, no exclusion, and no routing to alternatives such as get_question or list_open_questions. The agent must infer on its own that this is the polling/check-messages tool and how it relates to answering or asking questions.

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