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

With annotations already declaring openWorldHint=true and idempotentHint=false, the description still adds real value: it discloses that emails go out externally, that only people with an address are emailed, and that hard caps exist (one per day, three total, never after an opt-out). What it does not cover is the empty case — what happens when nobody is missing — or any failure behavior.

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?

Two sentences, front-loaded with the action and followed by the constraints, with no filler about the tool's importance. The phrase 'ready for the group chat and ready for one person' is slightly redundant, which keeps it from a 5.

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?

For a two-parameter mutation with no output schema, the description covers the action, the external side effect, the recipient filter, the returned message, and the rate limits — enough for an agent to call it correctly. The main omission is the no-op case when everyone has already recorded.

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 the schema already defines both parameters, making 3 the baseline. The description still adds meaning: 'emails a reminder to the ones with an address' clarifies the recipient filter behind `book`, and 'hands back a message ... ready for the group chat and ready for one person' explains the payload returned in the no-send mode that `also_email` controls.

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 states a concrete verb chain: identify who hasn't recorded, email the ones with an address, and return a message naming them. That is far more specific than the title alone and clearly separates it from siblings like send_it_out or read_the_messages, which do not compute a missing-participant set. It stops short of naming any sibling explicitly, so it lands at 4 rather than 5.

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?

Usage is implied by 'who is still out' — the agent can infer this is for chasing non-responders on a given book. There is no explicit statement of when not to use it, nor any pointer to an alternative tool for a different kind of reminder. The rate-limit sentences are behavioral constraints, not usage routing.

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