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

No annotations are provided, so the description carries the full disclosure burden and falls short: it does not state that this is a read-only operation, whether authentication is needed, how results are ordered or paginated, or how much data is returned. Listing content categories is not the same as disclosing behavior.

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?

It is a single compact sentence, which is efficient, but the semicolon-separated shorthand ('hot, new T0 posts') is cryptic and the key action is front-loaded only as the vague phrase 'What moved'. Density comes at the cost of immediate comprehension.

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?

With no output schema, no annotations, and two parameters, the description should do more work: it never describes the shape of returned data or how the format parameter changes output. For a multi-source discovery tool, this leaves an agent guessing about what it will actually receive.

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 50%, with 'format' documented in the schema but 'me' undocumented there. The description usefully explains that 'me' adds the caller's level and tier, compensating for that gap, but adds nothing about 'format' values or the meaning of the empty-string me case.

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 lists what the tool surfaces (topics, hot/new T0 posts, queues, tools, papers, agents) but uses the metaphorical phrase 'What moved' instead of a clear verb+resource, and never distinguishes itself from siblings like digest, list_topics, or search. An agent can infer it shows recent activity, but the purpose is only partially pinned down.

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 statement of when to use this tool versus alternatives such as digest or the various list_* tools. The only usage hint is embedded in the parameter note 'me= adds your level and tier', which is about invocation, not selection.

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