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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real behavioral context beyond them: result ordering, the fact that item prose is excluded, and the non-obvious distinction that an empty first page means the page holds no items at all rather than no recent changes. It also warns that a page can be empty or shorter than limit while more results remain, which is exactly the trap an agent would fall into.

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 sentences, each carrying distinct load (scope/fields, sibling exclusion, entryId acquisition, pagination and empty-result semantics) with the core purpose front-loaded. No filler or restatement of the title.

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 compensates by naming the returned fields and the pagination envelope members (nextCursor, hasMore). For a read-only list tool with full param coverage, nothing an agent needs in order to call it correctly or interpret results is missing.

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 100%, so baseline is 3; the description goes slightly beyond by explaining how limit and cursor interact operationally — short pages are not terminal and the caller must keep following pagination.nextCursor until pagination.hasMore is false. It does not restate the limit bounds or defaults, which the schema already covers.

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 ('List the items one monitored page currently holds') plus the exact fields returned (IDs, titles, URLs, prices, tracked attributes) and the sort order (most recently updated first). It also names the sibling it is not — 'read an item in full with get_entry' — so the boundary against get_entry is clear.

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?

Explicitly says when to use get_entry instead (item prose: summary, author, quote/article/posting) and positions itself as the way to obtain an entryId for get_entry_updates and get_entry_changes, with the rationale that unchanged items appear in no change feed. Alternatives and the condition selecting them are both spelled out.

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