Fetch and parse current enrolled-course pages for selected accounts so you can review active courses and track learning progress.
Fetch and parse the current enrolled-course pages for selected accounts.
| Name | Required | Description | Default |
|---|---|---|---|
| account_ids | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.9.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. 'Fetch and parse' implies a read operation, but it does not state whether the tool is safe/read-only, whether it requires logged-in accounts, what side effects (if any) it has, or how it handles errors or rate limits. Behavioral context is 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?
The description is a single, front-loaded sentence with no wasted words. It is efficiently structured and easy to parse.
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 covers return values, but the description is too sparse for a tool that likely interacts with external web pages. It lacks essential context about account selection, authentication requirements, and potential side effects, leaving the agent under-informed despite an output schema.
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%, and the description only vaguely refers to 'selected accounts' without explaining that account_ids is a list of account identifiers. It does not clarify what happens when account_ids is null (the default), whether it means all accounts, or what format the identifiers should take.
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 specific verb ('Fetch and parse') and resource ('current enrolled-course pages') scoped to 'selected accounts'. It does not explicitly differentiate from siblings like list_accounts or inspect_course, but the purpose is clear enough to distinguish from most.
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?
No guidance is given on when to use this tool versus alternatives such as inspect_course or list_accounts, nor on prerequisites like authentication state. The phrase 'for selected accounts' implies a selection mechanism but does not explain how to choose accounts or when the tool is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.