get_market_stats

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

No annotations are provided, but this is a read-only stats tool with no side effects expected. The description names the kind of data returned but doesn't disclose details like staleness of statistics, pagination, or whether it returns aggregate counts only. That is acceptable for a simple stats endpoint.

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?

One clear sentence, front-loaded with the purpose and useful examples, with no filler.

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 zero-parameter, no-output-schema statistics tool, the description is complete. It could mention whether the stats are real-time or cached, but the examples convey the content adequately.

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 exist, so there is no schema burden. The description adds value by enumerating example outputs (total listings, popular commodities), which is all an agent needs to know for zero-parameter invocation.

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?

Description clearly states it gets current statistics about the Mine Market platform and explicitly lists examples (total listings, popular commodities). This is a specific verb-resource pair that distinguishes it from siblings like search_listings and get_listing_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 implies it is the platform-level overview tool while siblings are narrower (search, details, commodity/country lists). It doesn't explicitly state when not to use it, but the scope is clear enough for an agent to select it for platform-level stats.

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