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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds only a fragment ('using live...') before truncating, so any behavioral value it might have conveyed about data freshness or method is lost. It provides essentially nothing beyond the annotations.

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 verbatim, wasting the front-load position, and the second sentence is truncated mid-clause ('using live...'), leaving the definition structurally incomplete. Not appropriately sized because it literally cuts off.

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 and no parameters, the description carries the full burden of explaining what the tool returns (denominators, thresholds) and when it applies. Because it is truncated and never explains its output or its boundary against screen_company, an agent cannot confidently invoke it.

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 (schema coverage 100%, empty properties), so there is nothing for the description to disambiguate. Baseline 4 applies, though the schema is trivial enough that no parameter guidance is required.

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 resource (the four Shariah equity standards: AAOIFI, Dow Jones Islamic Market, S&P Shariah, MSCI Islamic) and mentions their denominators and thresholds. However, the name 'list_standards' implies a reference-listing tool while the text describes screening 'a US-listed company,' which overlaps heavily with the sibling screen_company, leaving the actual purpose ambiguous. The sentence is also cut off, so the complete intent never lands.

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 when-to-use guidance, no prerequisites, and no mention of alternatives despite siblings like screen_company and screen_portfolio that appear to do the screening work described here. The agent has no signal for choosing this tool over those.

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