closeGridBot

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

Discloses settlement modes, required bot state, and rate limit of 3 qps per UID. No annotations provided, so description bears full burden. Could mention return behavior or error handling, but overall adequate.

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?

Concise, front-loaded with action, uses clear structure with line breaks and bullet-style list for modes. Agent hint adds value without 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?

Covers essential behavioral aspects (action, modes, state constraints, rate limit) given no output schema or annotations. Lacks details on error cases and grid_id source, but complete enough for typical usage.

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 0%, so description must add meaning. Provides detailed semantics for close_mode (enum meanings and hints), but grid_id is not explained beyond its implied role as bot identifier. Adds value for one of two parameters.

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?

Clearly states the tool closes a running spot grid bot, with specific verb and resource. Distinguishes from sibling close tools for other bot types (e.g., closeComboBot).

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?

Explicitly lists required close_mode with explanations of each option, and states the bot must be in NEW or RUNNING state. Includes agent hint for optimal mode selection. Lacks explicit exclusion of alternatives but context implies scope.

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