unprefer_tool

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

The description reveals the effect on ranking (falls back to score alone) but does not disclose any side effects, limitations, potential errors, or impact on other preferences. It is partially transparent but lacks comprehensive behavioral detail.

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 concise and efficient, consisting of two short sentences with no redundant information. It gets straight to the point without unnecessary elaboration.

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?

The description gives a basic understanding of the action and effect, but misses context such as the meaning of 'preference', how it interacts with other preference settings, or why 'HyperRoute' is relevant. Given the existence of sibling tools, some comparative context would improve completeness.

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?

The parameter tool_id is not described beyond its name. The description implies it is the tool to unprefer, but does not clarify what a valid tool_id looks like, how to obtain it, or whether it refers to a tool name or ID. Schema coverage is 0%, and the description adds minimal meaning.

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 clearly states the action ('Remove one preference') and the effect ('HyperRoute goes back to ranking that tool on its score alone'). It implies the tool_id parameter refers to the tool whose preference is removed, though it does not explicitly name the parameter.

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?

The description provides no guidance on when to use this tool versus alternatives like 'prefer_tool' or 'set_preferences'. It does not mention contexts, prerequisites, or situations where this tool is preferable.

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