Fetch the full list of teachers from an EduPage school to support staff directories, notifications, and role-based workflows.
Get all teachers in the school.
| Name | Required | Description | Default |
|---|---|---|---|
| subdomain | No |
Changes observed during successful MCP inspections.
v0.4.6Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. 'Get' implies a read-only retrieval with no side effects, which is transparent at a basic level, but it does not disclose authentication requirements, output format, or any behavior tied to the optional subdomain parameter.
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 filler. It is appropriately concise for a simple list tool.
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?
Despite the tool's low complexity, the description is incomplete: it omits parameter semantics, output shape, and any usage conditions. There is no output schema or annotations to fill these gaps, so the agent cannot fully predict the call's requirements.
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 never mentions the subdomain parameter. The property name gives some clue, but the agent gets no explanation of how subdomain affects results or how the default null should be interpreted.
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 uses a specific verb and resource: 'Get all teachers in the school.' It clearly states the scope (all teachers), but it does not explicitly distinguish itself from related sibling tools such as get_missing_teachers or get_my_students.
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 about when to use this tool versus alternatives, and there are no prerequisites or exclusions. The statement merely restates the operation; an agent is left to infer that this is the choice for a complete teacher list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.