search_fund_trades

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

With no annotations, the description carries the full behavioral burden. It implies a read operation via 'Search' but says nothing about pagination behavior, date-range constraints, result volume, or authentication, all of which matter for a 5-parameter query tool.

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 short sentence with the action front-loaded, so it is efficient. The trailing 'from bazaremali statistics' adds little value and is the one weak element.

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?

An output schema exists, so return values need not be explained. But for a 5-parameter search tool with zero annotation coverage and zero schema descriptions, the definition omits date-filter semantics, pagination, and any tie-breaker against the many sibling search tools, leaving it materially incomplete.

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, so the description must compensate and it does not. It never mentions start_date, end_date, symbol, limit or offset; only the self-evident parameter names carry any meaning, which is insufficient at this coverage level.

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 verb (Search) and a resource (commodity fund trades), which distinguishes it at a high level from sibling search tools for physical, futures, option, certificate and salaf trades. However, 'from bazaremali statistics' is opaque and the description never clarifies what a 'fund trade' is versus the other trade types, so the differentiation is only partial.

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 mention of prerequisites, and no routing to alternatives despite 13 sibling tools covering adjacent trade categories. The agent is left to infer selection purely from the tool name.

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