get_teachers

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

Annotations already indicate read only, non-destructive, idempotent. The description adds no further behavioral context (e.g., pagination, data freshness, rate limits). The word 'all' may be misleading as the schema includes filters for specific subsets.

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 sentence, but it omits essential context like pagination and result format, making it under-informative rather than suitably concise.

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 list tool with cursor pagination and 5 parameters, the description is inadequate. It does not mention that results are paginated, that it returns a list, or that parameters like search and label_id filter the results.

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?

All 5 parameters have descriptions in the schema (100% coverage), so the description adds no extra meaning. Baseline 3 is appropriate.

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 'Get all teacher records' clearly states the verb (Get) and resource (teacher records), and implies listing all records, distinguishing it from the singular sibling 'get_teacher'.

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 usage guidance is provided. The description does not specify when to use this tool versus alternatives like 'get_teacher' or filtering options, nor does it mention pagination or search behavior.

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