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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a non-destructive write. The description adds that it is user-initiated from the panel ('after the user tapped the panel's offer') and is not for the agent to call directly. It does not detail side effects or permissions, but that is less critical given the annotations and output schema.

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 tightly written sentences. The most important directive ('never call it yourself') is front-loaded, followed by the behavior. Nothing is wasted.

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 panel-only mutation tool with full schema coverage, annotations, and an output schema, the description provides enough context: who should call it, when, and what it does. No return-value explanation is needed because the output schema exists.

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% and the only parameter (timezone) is fully described in the schema with an IANA example. The description does not add any parameter-level meaning, 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?

States a specific verb ('Turns on reminders') and the resource (reminders tied to due cards), and explicitly scopes it to Flash's study panel. This distinguishes it from sibling tools such as start_study_session and set_limits, which are not panel-only.

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 'Used by Flash's study panel only; never call it yourself' and gives the triggering condition 'after the user tapped the panel's offer.' This is a clear when-to-use and when-not-to-use directive, leaving no ambiguity for the agent.

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