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

Annotations already establish read-only, idempotent, closed-world behavior, so the description wisely spends its space on domain semantics instead: a paused collection gets no new words or reviews, is excluded from daily goals and reminders, yet still studies normally when opened in the app. That is genuinely useful context an agent could not derive from the 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?

Front-loaded with the verb and resource, then a compact explanation of pause effects and the returned identifiers. It is dense and information-rich, though the middle clause about app behavior is slightly long for its weight.

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 an output schema present and a fully described single parameter, the description supplies exactly the missing piece: what 'on pause' means behaviorally and what identifiers each entry exposes. Nothing needed to call this tool correctly is absent.

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 targetLang is documented with examples, so the schema carries the parameter burden. The description only echoes 'for one language' without adding format, defaults, or any nuance beyond what the schema states; baseline 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 (lists) plus the exact resource (collections and sources for one language) and the distinguishing attribute (which are on pause). It is immediately separable from lingard_set_learning_pauses and lingard_get_learning_context by its read-only, pause-focused scope.

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?

The mention that entries carry 'the exact uuid, bookKey, and title that pause changes take' implies this feeds the pause-setting workflow, but the sibling tool is never named and there is no explicit when/when-not guidance. Usage must be inferred from context rather than read directly.

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