list_entries

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

With no annotations provided, the description partially covers behavioral traits by marking the operation as read-only with '[read]' and mentioning pagination. It lacks details on potential side effects, rate limits, or empty result behavior, but is adequate for a straightforward read operation.

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 extremely concise: a single sentence with a key usage tip. It is front-loaded with the read indicator, making it efficient and 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 the tool has 4 parameters (none required), no output schema, and a context of related tools, the description covers core purpose and sorting but omits important details like return format, pagination behavior (e.g., how page is used), or error handling. It is minimally complete.

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%, so the description must compensate. It mentions sort_by with its default value and pagination concept but does not describe page, per_page, or sort_order parameters. This is insufficient for an agent to fully understand parameter usage without inspecting the schema.

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 the tool lists recent entries across all feeds with pagination. The prefix '[read]' indicates the operation type, and 'List recent entries across all feeds' precisely defines the scope, distinguishing it from sibling tools like get_entry or search_feeds.

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 description provides explicit guidance on using sort_by='published' for newest first behavior, which is helpful. However, it does not directly compare against siblings or state when not to use this tool, though the context of sibling names implies it for general listing.

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