remind_list_entities

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), and the description adds genuinely new behavior: unread counts are included, paging is cursor-based, and the returned text is third-party-authored and must be treated as data rather than instructions. That untrusted-content warning is exactly the kind of context annotations cannot express.

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 sentences, zero waste: identity and scope first, entry-point role and paging second, security caveat last. Each sentence carries distinct, necessary information.

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?

With no output schema, the description carries the return-value burden and does so — listing entity types, unread counts, uuids, and the cursor. Combined with the annotation-covered safety profile, nothing needed to call this tool correctly 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 both parameters are already documented in the schema. The description restates that the query is an optional filter and the cursor comes from a previous call, adding no syntax or format detail beyond the schema, which is the expected baseline.

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 everything in the Remind sidebar — classes and chats') and scopes it precisely against the sibling tools remind_get_classes and remind_list_chats by covering both entity types in one call. It also declares what it returns (uuids, unread counts) so an agent can tell it apart without opening the schema.

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 frames itself as 'the entry point: it yields the uuids the other tools take', which routes the agent to call this before the uuid-consuming siblings, and notes the optional query filter and cursor paging. It stops short of naming specific alternatives or stating when not to use it (e.g. when a uuid is already known), so it is clear context without exclusions.

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