summaries

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

With no annotations provided, the description must disclose behavioral traits, but it only states a simple retrieval. It lacks information about data freshness, update frequency, rate limits, or any side effects. The tool's behavior is opaque beyond its basic function.

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, well-structured sentence that front-loads key information. Every word contributes meaning—there is no redundancy or filler. It achieves clarity with minimal text.

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 the tool has no parameters, output schema, or annotations, the description provides the essential purpose but lacks details on output structure, data source, or performance characteristics. For a simple tool, it is adequate but not 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 tool has no parameters (input schema is empty), so schema coverage is 100%. Per the rule for 0 parameters, baseline is 4. The description does not need to add parameter semantics, and it appropriately focuses on the tool's purpose.

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 that the tool retrieves 24-hour and 7-day market summaries for all pairs, specifying the verb 'Get', the resource 'market summaries', and the scope 'all pairs' with explicit time periods. This is specific and distinguishes it from sibling tools like ticker (single pair) or ticker_all (tickers without summary).

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 guidance is provided on when to use this tool compared to alternatives such as ticker_all, ohlc, or ws_snapshot_summary. The description does not mention any prerequisites, limitations, or typical use cases, leaving the agent without context for selection.

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