search_stats

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

No annotations are provided, so the description carries the burden. It describes the tool's purpose (showing provider faults and slowness) but does not explicitly state whether it is read-only, side-effect-free, or requires any authentication. It also doesn't describe the output format, though an output schema exists. The behavioral transparency is moderate; it gives context but not explicit guarantees.

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?

Two sentences with no fluff. The core purpose is stated first, followed by usage guidance. Every sentence adds value.

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 simple one-parameter tool with an output schema, the description covers the purpose and usage. It could mention what metrics are shown, but the phrase 'provider nào hay lỗi và chậm bao nhiêu' already conveys that. It is sufficiently complete for an agent to invoke correctly.

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 schema covers 100% of the parameter ('hours') with a description and default. The description references 'N giờ' which aligns with the parameter. No additional semantics are needed; baseline 3.

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 states a specific verb ('xem' – view) and resource (provider performance), and clarifies the time window ('trong N giờ gần nhất'). It clearly distinguishes from siblings (web_search, fetch_page) by focusing on statistics rather than search or page fetch.

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?

It provides explicit usage guidance: 'Dùng khi search trả kết quả kém hoặc chậm' (use when search returns poor or slow results), and states the purpose ('để biết nên đặt API key hay không' – to know whether to set an API key). It doesn't mention when not to use or alternatives, but the condition is clear.

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