queryGridDetail

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

The description implies read-only behavior with 'retrieves' and provides a rate limit of 10 qps per UID. Since no annotations exist, the description carries the full burden. It could be improved by explicitly stating no side effects, but the current wording is sufficient for a query tool.

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 well-structured with a field list, usage statement, rate limit, and agent hint. It is appropriately sized and front-loaded with key details. Slight room for improvement by combining the agent hint into the main usage guidance, but overall concise.

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?

For a one-parameter query tool with no output schema, the description sufficiently covers what the tool returns (listing many fields) and how to obtain the required grid_id. It lacks mention of pagination or error handling, but for a simple detail query, it is contextually complete.

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% (no description in schema), so the description must compensate. It explains that grid_id is a numeric ID obtained from createGridBot or grid list queries, adding context beyond the raw integer type. However, it does not specify format or constraints, making it adequate but not exemplary.

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 it retrieves comprehensive details of a spot grid bot, listing specific fields (symbol, price range, profit metrics, status, etc.). It distinguishes from sibling tools like getFGridDetail by specifying 'spot grid bot', ensuring the agent selects the correct tool for spot grid details.

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 explicitly says 'Use this when you need to check the current state, performance, or configuration of a specific grid bot' and provides guidance on obtaining grid_id. However, it does not explicitly mention when not to use it or point to alternative tools like getFGridDetail for futures grids, leaving some ambiguity.

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