remind_list_entities

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds useful context beyond that: results include unread counts, mirror the app's rendering, expose uuids for downstream tools, and support cursor paging.

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?

Three tight sentences with zero waste; the core purpose and entry-point role are front-loaded before the filtering and paging notes.

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, but the description covers the essentials an agent needs: what is returned (classes, chats, unread counts), that uuids feed other tools, and how to page. A little more on return ordering or result size would make it fully self-contained.

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?

With 100% schema description coverage, the schema already documents both parameters. The description reiterates the query filter and cursor paging in prose without adding format, syntax, or edge-case detail beyond the schema, so the baseline of 3 applies.

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 names a specific verb and resource ("List everything in the Remind sidebar — classes and chats") and clarifies scope ("as the app itself renders it, with unread counts"). It implicitly distinguishes itself from siblings like remind_get_classes and remind_list_chats by being the combined entry point.

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?

"This is the entry point: it yields the uuids the other tools take" gives clear when-to-use context and explains its role relative to the other tools. It stops short of explicit exclusions (e.g., when to prefer remind_get_classes or remind_list_chats directly).

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