get_missing_teachers

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must carry the behavioral burden. It discloses the default date behavior but does not explain what 'missing' means operationally, the return format, potential side effects (though 'get' implies read-only, it is not stated), or any permission requirements. This is minimal disclosure.

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 short sentence, which is concise, but it omits critical details. It does not structure information about parameters, usage context, or output; it is under-specified rather than efficiently complete.

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 two parameters, no annotations, and no output schema, the description is severely incomplete. It fails to define 'missing', provide parameter details, describe expected output, or mention any preconditions like login. An agent would be unable to reliably invoke this tool.

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?

Neither parameter is described in the schema or description. date_str can be inferred as the date to check, with a default of today, but its format is unspecified. subdomain is entirely unclear, likely the school subdomain, but not explained. With 0% schema coverage and no textual explanation, agents cannot correctly supply parameters.

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 states the action: retrieving teachers missing on a date, with a default of today. It distinguishes itself from sibling get_teachers through the 'missing' qualifier, making the purpose specific. However, it does not explicitly contrast with other date-related tools like get_absences, so it's clear but not fully differentiated.

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 provided on when to use this tool versus alternatives such as get_teachers or get_absences. There is no mention of preconditions like authentication or data context, leaving an agent without basis to choose it over other tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.