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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower. The description adds real substance: the two-phase methodology, the specific AAOIFI/Dow Jones/S&P/MSCI debt screens applied, and that output links to halal alternatives in the same industry.

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?

Front-loads the core question, then details the screening flow and alternative-link behavior in a compact block. Each sentence contributes, though the standards list is dense and slightly packed.

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 carries the burden of explaining results, and it does so by outlining the screening steps and that alternative recommendations are returned. The main gap is a lack of explicit routing guidance versus sibling screening tools.

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% and there is only one parameter, so the baseline would be 3. The description adds meaning beyond the schema by stating that a company name (nvidia, philip morris) is also accepted, not just the ticker the schema documents.

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 and resource: it screens a US-listed stock for halal status and lays out the exact screening sequence (business activity, then four named debt standards). This clearly separates it from stock-adjacent siblings like halalornot_check_fund and halalornot_check_crypto.

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 stock focus and the note that a company name works, so an agent can infer it is the tool for equities. However, it never explicitly says when to prefer this over mizan_screen_company or halalornot_ask_is_it_halal, nor states exclusions for non-US listings.

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