Barakah Halal Stock Screen

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds substantive behavior beyond that: the exact screening thresholds applied, the exchange coverage (NASDAQ, NYSE, ASX, Bursa, SGX), and the fact that verdict-change dates are returned from a public ledger. It does not mention rate limits or auth, which is a minor gap.

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?

The screening criteria are front-loaded immediately after the verb, followed by return behavior, coverage, and input format in descending priority. No sentence is filler; even the coverage and ticker clauses prevent wrong invocations.

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?

With no output schema, the description correctly compensates by stating what comes back (a verdict plus the dates it changed). For a single-parameter read tool with annotations covering safety, this is nearly complete; only the exact response shape and any rate limits are left unspecified.

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 coverage is 100%, so the baseline is 3, but the description meaningfully enriches the single parameter by showing exchange-suffixed ticker formats (NVDA, CSL.AX, 1155.KL, D05.SI) that clarify how non-US listings must be passed. This adds real syntax guidance beyond the schema's own example.

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 gives a specific verb (screen) and resource (a listed company), plus the explicit criteria family (AAOIFI-style: business activity, debt/cash <30% of market cap, interest income <5% of revenue). It is clearly distinct from a generic stock lookup, though it never names the sibling recent_halal_verdict_changes to route between them.

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?

Usage is implied by the phrasing 'Pass a ticker ... or a company name,' which tells the agent how to invoke it, but there is no explicit when-to-use or when-to-prefer-the-sibling guidance. An agent must infer that this is the per-company deep screen while the sibling is the changelog feed.

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

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

readOnlyHint=true already tells the agent this is a safe read. The description adds real context beyond that: results are dated and cover both directions of the flip (cleared or broke the screen). It does not disclose pagination, ordering, or how far back 'recently' reaches.

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 tight sentences with the core behavior front-loaded. The trailing clause 'A dated public record most screeners don't show' is promotional rather than operationally useful, costing a little 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?

For a read-only, single-parameter listing tool with no output schema, the description covers what is returned (stocks, with dates, both flip directions). Only the definition of 'recently' and result ordering are left unstated.

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?

There is one parameter (limit) and schema description coverage is 0%, so the description contributes nothing to parameter meaning. The schema itself carries type, default 10, and min/max bounds, which makes the gap tolerable, but 'limit' is never referenced in prose.

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 resource (stocks whose halal screening verdict recently flipped) and the scope (recent, dated). A reader can distinguish it from check_halal_stock's single-stock lookup, though the sibling is never named, so the differentiation is inferred from scope rather than stated.

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?

Usage is implied: fetch this when you want a changelog of verdict flips rather than a single-stock check. There is no explicit when-to-use, when-not-to-use, or mention of check_halal_stock as the alternative, so an agent must infer the routing.

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