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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and closed-world behavior, so the safety profile is covered. The description adds useful context about 'live' profile data and duplicate avoidance, but says nothing about pagination, limits, or what 'live' implies operationally.

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 well-formed sentence with the return contents front-loaded and the purpose appended. No filler and no repetition of the title.

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?

The output schema and annotations reduce the disclosure burden, and the description conveys the overall purpose. However, for a 7-parameter context-fetching tool with zero schema coverage and no sibling routing guidance, the definition leaves too much for the agent to infer about parameter behavior and tool selection.

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 description coverage is 0% across 7 parameters, so the description carries the full burden. It conceptually names level, topic, and collection context, but never explains targetLang, count, excludeLimit, or collectionUuid vs collectionTitle, leaving several parameters opaque.

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 ('Returns') and enumerates the resources returned: profile level, topic, collection context, and existing words, plus the purpose (suggesting level-appropriate non-duplicate cards). It does not differentiate itself from siblings like lingard_get_learning_context or lingard_get_collection_gaps, so an agent must infer the boundary.

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 use case is implied by 'the context for suggesting level-appropriate new cards that are not duplicates', but there is no explicit when-to-use guidance, no exclusions, and no named alternative among the many lingard_get_* siblings. Usage is inferable but not directed.

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