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

Annotations cover read-only and open-world behavior, so the bar is lower, yet the description still adds real value: excerpts are untrusted content (a prompt-injection warning), they are not full articles, and pagination terminates when next_source_offset is null. It omits result volume/format expectations, but the safety-relevant context is well disclosed.

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?

Four compact sentences, front-loaded with purpose, then the category rule, pagination instruction, and trust caveat. Every sentence carries information, though the parenthetical about category assignment is dense.

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?

No output schema exists, and the description explains the cursor field and excerpt nature but not the shape of returned batches or the semantics of half the parameters. Adequate for calling it, incomplete for calling it optimally.

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% across 7 parameters, so the description must carry the load. It explains category values and the offset cursor, but leaves days, limit, query, and the 44-value sources enum entirely undefined, which is a substantial gap for a filtering/retrieval tool.

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 verb and resource — retrieving recent posts from fixed public feeds — and clarifies the feed model (categories belong to sources, not articles). It doesn't explicitly name the list_sources sibling, only alluding to it via 'Manual-only sources are listed separately', so differentiation is inferential rather than stated.

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?

Gives concrete operational guidance: pick category ai_development or agent_flow for source batches, and follow next_source_offset until null. However, it never says when to use this tool versus list_sources, nor how to choose between the sources, category, and query parameters.

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