get_selected_bookmakers

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

The description indicates it is a read operation on the authenticated user's selection, but with no annotations, it does not detail side effects, authentication needs beyond implication, or rate limits. It is adequate but minimal.

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?

A single sentence that precisely conveys the purpose. Every word earns its place; no waste.

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?

Without an output schema, the description should hint at the return format or structure. It only mentions 'selected bookmakers' but does not specify if these are IDs, names, or objects. Complexity is low, but completeness suffers from lack of detail on output.

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?

There are no parameters, and the schema coverage is 100%. The description adds no parameter information because none exists. Per calibration, 0 parameters with full coverage gives a baseline of 4.

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 verb 'Get' and the resource 'the authenticated user's currently selected bookmakers'. It distinguishes from sibling tools like 'clear_selected_bookmakers' and 'select_bookmakers' by implying viewing vs. modifying.

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?

While no explicit when/when-not guidance is given, the description's focus on 'currently selected' implies it is for viewing the current selection, contrasting with the setting/clearing siblings. It is straightforward for a simple getter.

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