select_bookmakers

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

No annotations are provided, so the description must carry all behavioral information. It only states 'add' but does not disclose side effects (e.g., whether it replaces or appends, if it requires authentication, or any limits). The minimal description leaves the agent uncertain about the tool's behavior.

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 sentence, very concise, and front-loaded with the action. It efficiently conveys the core purpose, though it could be slightly more structured by including a brief usage hint. There is no wasted text.

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 single parameter and no output schema, the description is too minimal. It does not explain the meaning of 'selection', how it interacts with other tools (e.g., getting odds), or any constraints. The agent lacks context to use the tool effectively.

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 coverage is 100% and the schema already describes the parameter format (comma-separated names). The tool description adds no extra meaning beyond the schema. Baseline 3 is appropriate as the description does not enhance understanding of the 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 clearly states the action ('Add') and the resource ('bookmakers to the authenticated user's selection'). It distinguishes from sibling tools like 'clear_selected_bookmakers' and 'get_selected_bookmakers', which have different purposes. However, it does not elaborate on what 'selection' means in the broader 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when it should be invoked, or any context about its role (e.g., before getting odds). No exclusions or alternatives are referenced.

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