wilma_homeworkRetrieve recent homework entries by lesson, newest first, for a specific child or every child on the account.
Recent homework entries by lesson, newest first.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| student | No | Child's name or student number. Omit to include every child on the account. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds the useful 'newest first' ordering, but never defines how far back 'recent' reaches or whether results are truncated by a default limit.
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 front-loaded sentence with zero filler; the ordering constraint is stated immediately. Nothing extraneous is present.
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 simple two-parameter read tool with rich annotations, the definition is minimally workable, but with no output schema the description should at least characterize what a homework entry contains and what default window 'recent' covers.
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 schema documents 'student' well but leaves 'limit' with only min/max bounds and no semantic description; the tool description adds nothing about either parameter, so the 50% coverage gap is not compensated.
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?
Names a specific resource (homework entries) with a clear ordering guarantee (newest first) and a scoping hint (by lesson). It is distinguishable from siblings like wilma_grades or wilma_lesson_notes, though 'by lesson' is ambiguous about whether results are grouped or merely labeled.
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 on when to call this versus wilma_grades, wilma_lesson_notes, or wilma_summary, all of which could plausibly surface homework-like data. The agent must infer selection from tool names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.