list_recent

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

With no annotations, the description carries full burden. It states it lists posts and the returned fields, implying a read-only operation. It does not disclose potential limits (e.g., max days) or sorting behavior, but is reasonably transparent.

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 concise with two sentences: first states the action, second gives usage hint and output fields. No wasted words.

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?

Given one parameter, no annotations, and the existence of an output schema, the description covers the core functionality, usage hint, and output format. It could mention the lack of other filtering options or the recency limit.

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 input schema has 0% description coverage; the description refers to 'last N days' which maps to the 'days' parameter but does not explicitly mention the parameter or its default value. It adds some clarity but not enough for full compensation.

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 'List posts from the last N days' specifying the verb and resource. It provides a usage hint 'Use to orient before searching' which distinguishes it from search tools, but does not explicitly differentiate from the sibling 'discover'.

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 'Use to orient before searching' gives context for when to use this tool for initial overview. However, it lacks explicit guidance on when not to use it or alternatives like 'search_news' or 'get_post'.

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