Coach — the next lesson in a subject, deterministically. Omit after for the first unit; pass a unit id for the one that follows it. subject selects the path.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | ||
| subject | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It shares that the operation is deterministic and how sequencing works. It does not disclose return format, side effects, or failure modes. The 'deterministically' label adds some behavioral context, but the description remains minimal.
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?
Three short sentences, front-loaded with the core purpose, then usage details. No wasted words.
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 tool with only two optional parameters and no output schema, the description covers the main usage. It could hint at the return value or error behavior, but overall it is sufficiently complete for the tool's simplicity.
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?
The input schema has no parameter descriptions (0% coverage), but the description explains both parameters: `after` is a unit id for the previous lesson, and `subject` selects the path. This provides essential semantics beyond the bare schema, though it lacks format examples.
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 clearly identifies the tool as providing the next lesson in a subject, with a specific deterministic sequencing behavior. It distinguishes itself from sibling coach_* tools by emphasizing 'next' and the `after` parameter. Though not using an explicit verb like 'gets', the resource and action are unambiguous.
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?
It provides explicit instructions on how to use the `after` parameter: omit for first unit, pass unit id for next. It also explains `subject` selects the path. However, it does not explicitly contrast with alternative coach tools or state when not to use it, so it falls short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools are near-duplicates: read_passage and resolve both fetch WEB text for a reference; word_study already includes every occurrence that word_occurrences returns; coach_next and coach_recommend both answer 'what's next.' Search/locate/cards_browse also overlap as discovery entry points, making tool selection ambiguous despite detailed descriptions.
Most names follow an object_verb snake_case pattern (cards_browse, study_create, seal_fetch), but there are many bare verbs/nouns (ask, audit, resolve, verify, canon, harmony) and inconsistent singular/plural pairs (card_get vs cards_browse, group_create vs groups_list, want_open vs wants_list). No camelCase, but the convention is not uniform.
86 tools is an extreme count for any single MCP server, far beyond the 3-15 well-scoped range; even a broad platform would be hard for an agent to navigate. Many tools belong to unrelated subdomains (coach, steward, mesh, calendar), making the surface unwieldy.
The want/offer flow has no accept/close tool, so an agent can open a want and offer a source but never see it resolved. Group and calendar coverage are one-directional (create/join only; no leave/delete/list/update), and there is no badge listing or way to update a study group. Core reading/verification/shelf flows are solid, but lifecycle gaps remain.