get_model_drift

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about read-only safety, what 'drift observations' contain, whether results are paginated or capped, or how the defaults behave. Only the weak implication of 'Check' suggests a read operation.

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?

It is a single short sentence with no wasted words and the purpose is front-loaded. However, extreme brevity here reflects under-specification rather than economy, so it cannot score higher.

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?

Although an output schema exists (so return values need not be explained), the tool has two wholly undocumented parameters and zero annotations, and the description never supplies the missing scope, filtering, or safety context. It is not complete enough for reliable invocation.

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% for both parameters. The description never mentions 'days' (time window, default 7) or 'model' (default empty string, presumably meaning all models) — the empty-string default is particularly non-obvious and undocumented.

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 resource ('AI model behavioral drift observations') but the verb 'Check' is vague and could mean fetch, validate, or alert on. It gives no differentiation from siblings like get_ai_status or get_ai_incidents, leaving the agent to guess which is the right drift-related tool.

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?

There is no statement of when to use this tool versus alternatives, nor any mention of prerequisites, time windows, or filtering intent. The agent must infer everything from the name alone.

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