Islamic securities trading by investor type

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

Annotations already state that this tool is read-only, idempotent, non-destructive, and open-world, so the description does not need to explain safety. It usefully adds behavior that annotations cannot convey: values are full numbers in rial even though the source site abbreviates with a B suffix, and rows are newest-day-first. Ordering and units are real additions, but rate limits and the shape of the response are not covered.

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 short sentences put what the tool returns first and when to use it second. No filler or repetition, and the unit caveat is packed into a compact parenthetical.

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?

No output schema exists, so the description has to cover return values; it does so by describing the trading-value breakdown, row ordering, and units. One ambiguity remains: the schema notes 10 rows per page, but the description never says whether pagination walks across days or across investor/type rows for a single day. That matters for correct paging.

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?

With schema description coverage at 100%, the schema fully documents both the 'by' enum and the 'page' bounds. The description gestures at the 'by=investor' dimension ('by who bought and sold') and at ordering, but adds no syntax or format detail beyond what the schema already supplies. The baseline score of 3 is appropriate.

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 names a specific verb and resource: daily trading value of Islamic financial securities (sukuk, treasury bills) broken down by buyer and seller. It is easy to separate from siblings such as ifb_yields or ifb_quote, which cover different datasets. It stops short of naming an alternative, so it is clear but not fully differentiated.

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 second sentence supplies a clear use case: observing central-bank open market operations and bank or fund activity day by day. That context is enough for an agent to choose this tool over an unrelated sibling. The description gives no explicit exclusions or mentions of alternatives, which keeps it from a 5.

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