List graded Chinese readings with their computed HSK levels to choose practice texts by difficulty.
List the graded Chinese readings with their computed HSK level.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden. It implies a read-only listing but says nothing about ordering, pagination, result count limits, or whether the HSK level is always present versus computed on demand.
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 sentence with no filler, and the resource and its distinguishing output field are front-loaded. Every word earns its place.
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 trivial no-parameter list tool the description is nearly sufficient, but with no output schema the agent still lacks any sense of what a 'reading' record contains or how large the listing is. The mention of the computed HSK level is the one piece of return-value context provided.
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 tool takes zero parameters, so there is no parameter semantics to document; the baseline for a 0-param tool applies. The description correctly avoids inventing filtering options that the empty schema cannot honor.
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?
Specific verb ('List') plus resource ('graded Chinese readings') with the notable attribute that the result includes a computed HSK level. It is distinguishable from get_reading by the plural/list framing, though it never names that sibling to make the contrast explicit.
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?
Usage is only implied: an agent can infer this is for enumerating all readings rather than fetching one, but the description offers no explicit when-to-use, no conditions, and no pointer to get_reading as the single-item alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.