my_preferred_tools

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

The description implies a read-only operation by using the verb 'List', and the context of using it before changing/removing suggests it is non-destructive. However, it does not explicitly state that no data is modified, which would have made it fully transparent. Since no annotations are present, the description carries the burden, and it is mostly clear but not explicit.

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 two sentences that are succinct and direct. It front-loads the main purpose ('List the catalog tools...') and immediately provides usage context. No unnecessary words or redundancy.

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?

Given the absence of parameters and output schema, the description provides all necessary context: what the tool does, when to use it, and why (to get the right ID). It is self-contained for an agent to invoke it correctly.

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 tool has zero parameters, so the empty parameter schema is fully covered. The description does not need to elaborate on parameter meanings. According to the rubric, 0 params results in a baseline of 4, and no additional information is required or missing.

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 tool lists catalog tools that the user has asked to favour, including margin and note. It identifies the resource (catalog tools) and the action (list), and distinguishes it from related tools like 'prefer_tool' and 'get_preferences' by focusing on the user's favouring context.

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?

Explicit guidance is provided: 'Call this when the user asks what HyperRoute leans toward, or before changing/removing one so you use the right id.' This gives concrete scenarios for invocation and explains the practical benefit of obtaining the correct ID before modifications.

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