clear_selected_bookmakers

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

Describes destructive action ('clear') and rate limit. No annotations provided, so description carries burden; could mention error behavior on rate limit hit, but adequate for tool with no parameters.

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?

Two short sentences, front-loaded with action and constraint. No wasted words.

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?

Covers purpose and rate limit for a simple no-param, no-output-schema tool. Lacks return value info but acceptable given simplicity.

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?

No parameters, so description adds no parameter info. Per rules, 0 params baseline is 4, even with 100% schema coverage.

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?

Clear and specific: 'Clear all selected bookmakers for the authenticated user.' Distinguishes from siblings 'get_selected_bookmakers' and 'select_bookmakers' by being the opposite action.

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?

Mentions rate limit of once every 12 hours, giving a clear constraint. Lacks explicit comparison to alternatives, but context with sibling tools makes it clear.

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