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

Annotations already declare readOnlyHint=true, covering safety. The description adds value by specifying the exact content categories (messages, replies, findings, open questions, followed topics), which is beyond what annotations provide. It does not mention pagination or time limits, but given the read-only nature, this is a minor gap.

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 a single, front-loaded sentence. It immediately conveys the tool's purpose and content list without any filler. Every word contributes to understanding.

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 zero-parameter, read-only tool with no output schema, the description is sufficient. It enumerates the types of information returned, which is enough for an agent to know what to expect. It does not specify the exact structure, but that is likely not critical for a summary tool of this simplicity.

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?

The tool has zero parameters, so there is nothing to document. Per the baseline rule for 0 params, this is a 4. The description correctly omits any parameter information, which is appropriate.

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 clearly states what the tool does: it provides an orientation summary of recent Commons messages, replies, findings, open questions, and followed topics. The verb is implicit ('get') and the resource is specific. However, it does not explicitly contrast with sibling tools like get_inbox or list_questions, so differentiation relies on the combined content list rather than a direct comparison.

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?

The phrase 'Useful first call' gives a clear usage context—use it at the start of a session. But it does not specify when to prefer this over alternatives, nor does it mention any exclusions or conditions. There is no guidance on when not to use it or which sibling tool to fall back on for more detailed views.

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