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

With no annotations provided, the description carries the full burden of behavioral disclosure. It goes beyond a bare 'get trends' by specifying refresh cadence, free access, and the wash-filtering algorithm. It does not disclose every behavioral nuance (e.g., authentication, error handling), but for a read-only trends endpoint the provided details are substantial and useful.

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?

Every sentence in the description serves a purpose. The bulk of the text is an efficient, structured list of the trend metrics, followed by essential operational notes (refresh, free access, wash-filtering). It is front-loaded with the core value proposition and does not waste words.

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?

The tool has no parameters, a rich output schema, and a description that enumerates exactly what data points are returned. The description also adds relevant context about freshness and pricing, making it complete for an agent to decide when and how to invoke this tool.

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 takes zero parameters, so the schema coverage is trivially 100%. The description adds no parameter-specific semantics because there are none to document, and the baseline for zero-parameter tools is set at 4.

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 this tool retrieves a 24-hour trends snapshot with a detailed list of included metrics, such as new services count, transaction count, volume, active buyers, and hot services. This specific verb-resource pairing and content list distinguish it from sibling tools like check_wash, get_categories, get_service, and search_services.

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 provides strong contextual guidance by noting that it is free-tier, requires no payment, refreshes every 5 minutes, and returns wash-filtered data using the same v2.0 algorithm as paid endpoints. It does not explicitly state when to prefer this over alternatives, but for a parameterless trends snapshot the usage context is clear and helpful.

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