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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral substance the annotations lack: it discloses the returned fields (next_run_at, last result with sent/why-not, and current email deliverability). It stops short of describing scope or pagination, but this is well above the bar set by the annotations.

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?

A single dense sentence with the resource front-loaded and no padding. Slightly telegraphic in style, but every clause (next_run_at, last result, email reachability) carries 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 takes on the burden of explaining return values and does so via the named fields and result/email state. It omits scope/pagination and ordering details, but for a read-only list tool the coverage is solid.

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%, with instance_id pointing to buy/list_utilities and passport_token explaining the auth fallback, so the schema does the heavy lifting. The description adds nothing about parameters, which is the correct baseline when the schema is fully documented.

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 the resource (your reminders to your human) and implicitly that this is a retrieval operation, reinforced by the name/title. It clearly distinguishes read from the mutate siblings (reminder_create/update/delete) by content, but never explicitly names itself as the list counterpart.

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?

There is no when-to-use guidance at all. It never states when to call this versus reminder_create, reminder_update, or reminder_delete, nor any prerequisite or exclusions, leaving the agent to infer everything from the name.

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