search_certificate_trades

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about authentication, rate limits, pagination behavior, or what a search returns. An output schema exists, which offsets some of this, but the mutation-free read profile is only assumed, 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?

A single front-loaded sentence with no filler, which is structurally clean. However, the brevity comes at the cost of substance rather than being an instance of efficient density, so it reads as under-specified rather than concise.

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 output schema means return values need not be described, but for a 5-parameter date-filtered search with a required start_date, an agent still lacks the date format, pagination defaults, and any usage context. What is present is a bare minimum for a tool of this complexity.

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?

Schema description coverage is 0% across 5 parameters, and the description adds no parameter meaning at all — not the date format for start_date/end_date, nor the filtering semantics of symbol, nor how limit/offset interact. Parameter names are largely self-explanatory, which keeps this above the floor, but the description does no compensating work.

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?

States a specific verb (search) and resource (commodity deposit certificate trades), and names the data source (bazaremali statistics). It is distinguishable from siblings like search_physical_trades and search_futures_trades by the certificate asset class. It stops just short of 5 because it never clarifies what a 'certificate trade' record contains.

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?

There is no when-to-use guidance, no criteria separating it from the other search_* siblings, and no mention of prerequisites for reaching the bazaremali statistics source. The agent is left to infer scope from the tool name alone.

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