get_teacher_analytics

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

With no annotations, the description carries full responsibility for behavioral disclosure. It mentions 'shrinkage-adjusted, time-decayed' but does not explain what these adjustments mean operationally, whether the operation is read-only, or what the response contains. This is insufficient for an agent to anticipate side effects or output.

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, compact sentence that gets to the point quickly. It is appropriately sized for the tool's simplicity, though it could be slightly more informative without becoming verbose.

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 that presumably returns analytics, the description lacks essential context such as what metrics are included, how the adjustments affect results, and the nature of the output. With no output schema and no annotation, the description leaves too much to inference for an agent to fully understand what it will receive.

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 schema provides no meaning for 'teacher_id'. The description does not mention or clarify the parameter either, leaving the agent to infer from the name alone. The description fails to compensate for the lack of schema documentation.

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 states a specific verb ('Get') and resource ('teacher analytics') with two descriptive modifiers ('shrinkage-adjusted, time-decayed') that add specificity and distinguish it from sibling tools like get_teacher_profile and get_teacher_reviews. It is clear in intent, though 'analytics' is somewhat broad without further detail.

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_teacher_profile, get_teacher_reviews, or compare_teachers. The description lacks any context about typical use cases or conditions for selection.

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