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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior. The description adds useful domain context by naming the four standards (AAOIFI, DJIM, S&P, MSCI) and their basis in published Shariah equity criteria, but it does not disclose what is actually returned or clarify the mismatch with its screening narrative.

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 first sentence merely restates the title, and the second trails off with an incomplete fragment 'using live...'. The description is both redundant at the front and truncated at the end, so no sentence is fully earning its place.

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 parameters and no output schema, the description is the only source of information about what this reference-style tool returns (the standards, denominators, thresholds), yet it is cut off mid-sentence and never states the return shape or how the screening criteria are organized.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; no schema-level semantics are needed.

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 title and name promise a listing of four standards, but the body pivots to describing a screening operation against a US-listed company. With zero parameters the tool cannot actually screen a company, so the stated purpose is inconsistent with the tool's shape and leaves the agent unsure what it returns.

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 indication of when to call this versus siblings such as screen_company or screen_portfolio. The description mentions a screening flow that arguably belongs to screen_company, which actively misleads about tool selection rather than guiding it.

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