get_market_overview

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

With no annotations, the description must fully disclose behavior. It mentions returning 'current blockchain block' and 'TON price to USDT' but omits critical details: whether it makes external calls, caches data, requires authentication, or has side effects. Given zero parameters, it is likely read-only, but this is not stated.

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 concise sentence that immediately conveys the tool's purpose. It is front-loaded with the main action and resource. However, it could be slightly more structured (e.g., separate block and price info).

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 no parameters and the existence of an output schema (which should document return values), the description is minimally adequate. However, it only mentions block and price, which may not fully represent a 'market overview' (e.g., volume, market cap missing). The absence of the output schema limits assessment, but the description could be more comprehensive.

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?

The input schema has zero parameters and schema description coverage is 100%. Per guidelines, 0 parameters baseline is 4. The description adds no parameter info, but none is needed since there are no 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?

The description clearly states the tool provides a market overview for TON, including current blockchain block and TON/USDT price. The verb 'get' and resource 'market_overview' are explicit, but no differentiation from siblings like get_blockchain_info or get_token_price is provided.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus the sibling tools (e.g., get_blockchain_info for detailed blockchain data or get_token_price for price alone). There is no mention of context or alternatives.

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