rank_teachers

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

With no annotations, the description must carry the full behavioral burden. It states the operation but does not say whether it is read-only, how the confidence threshold filters results, what ordering is applied by default, or what the result contains. The text mostly restates the tool's purpose rather than disclosing behavior.

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 single sentence is efficient and front-loaded, but it is under-specified rather than concise: for a five-parameter tool with no parameter descriptions, this brevity sacrifices needed information.

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?

With no annotations, no output schema, and no property descriptions, the description leaves an agent unable to call the tool correctly: metric values are undefined, threshold semantics are unknown, and optional filters/order are not explained.

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%, so the description must compensate. It maps only two of five parameters (metric and confidence threshold) and gives no valid values or syntax for metric; limit, descending, and department_id are entirely unaddressed.

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 names a specific verb ('Rank') and resource ('teachers'), and the ranking focus distinguishes it from searching or profile siblings such as search_teachers and get_teacher_profile. However, it never references alternatives like rank_departments, so differentiation is implicit rather than 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?

No guidance is given about when to choose ranking over search_teachers or get_teacher_analytics, nor any exclusions such as which confidence values or departments are appropriate. The only implied context is that the tool is for ranking, which does not help an agent decide among the many sibling tools.

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