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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description contributes only the sequence of the screen (business first, then debt) and a truncated 'using live...' clause that never completes, leaving the data source and output nature undisclosed.

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 two sentences merely restate the name and title, and the description is cut off mid-sentence ('using live...'), so it is both redundant at the front and incomplete at the end. Space is spent on repetition rather than on the distinguishing information.

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 input schema, no output schema, and no parameters, the description carries the full burden of explaining what a caller gets back — yet it is truncated and never says whether the result is the standards themselves or a company screening verdict. Too much is left unresolved for a zero-parameter tool whose siblings overlap heavily.

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 zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description does not need to compensate for any schema gaps.

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 name and title promise a reference listing ('the four standards, their denominators and thresholds'), but the description describes an action — screening a US-listed company against those standards — which is what the sibling mizan_screen_company appears to do. The agent cannot tell whether this tool returns a static reference table or performs a screen, so the purpose is genuinely ambiguous rather than vague.

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?

No when-to-use guidance and no routing to alternatives, even though mizan_screen_company, mizan_screen_portfolio, and halalornot_screen_stock are close siblings that need to be disambiguated from this one. The description only states a method, not conditions for choosing it.

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