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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile, so the bar is lower. The description does add value beyond that by naming the warning categories (scam failures, invented data, inconsistency), which tells the agent what kind of risk signal it is retrieving, though it says nothing about return shape or volume.

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?

One sentence, no padding, and the resource and warning taxonomy come first. It is phrased as a noun fragment rather than a directive sentence, which slightly weakens front-loading of the action.

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 single-parameter read-only tool with no output schema, the description supplies enough to know what is returned (flagged models and the reasons). It stops short of explaining result structure or how many models come back per task, but nothing critical for invocation is missing.

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 100% and the single 'task' parameter has an enum plus its own description and a pointer to list_tasks, so the schema carries the full burden. The description adds nothing about the task id beyond what the schema already states, which is the baseline 3 for a fully documented parameter.

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 identifies the resource returned (models RealRun flagged as not recommended or needing caution on a task) and gives examples of warning kinds, so an agent knows what it gets back. It lacks an explicit verb ('returns a list of...') and does not contrast itself with the sibling recommend_model or get_scores, so it stays a step short of a 5.

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 call this versus get_scores or recommend_model, and no prerequisites or sequencing guidance. The agent must infer that this is the safety-check counterpart to the scoring tools entirely on its own.

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