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

Beyond readOnlyHint=true, the description discloses the return shape, the exact enum-like severity values ('red' or 'amber', red first), the available:false semantics, the skipped-screen caveat for empty flags, the data source, and the API-key/operator-config requirement. This is a rich behavioral disclosure that annotations alone would not provide.

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 action and the return contract, and the parenthetical screen list is dense but informative rather than filler. The long enumeration with 'and others' is slightly unwieldy, but every sentence carries usable 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 output schema, the description fully specifies the return object ({ticker, available, flags, count} and the flag fields), the severity domain, and the failure mode. It also covers the auth prerequisite, leaving nothing an agent needs in order to call and interpret the tool correctly.

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 single parameter (ticker) is fully documented in the schema at 100% coverage, so the schema does the heavy lifting. The description adds no format or constraint detail beyond what the schema already states, giving the expected baseline of 3.

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 ('Run 15 red-flag screens on a ticker') and enumerates the actual screens with their thresholds, so an agent knows exactly what is computed. The enumerated content (short interest, Altman Z, net leverage, etc.) cleanly separates it from generic sibling tools like get_fundamentals or ol_fundamentals_screen.

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?

Tells the agent how to interpret results ('a flag is a question to investigate, NOT a sell signal') and names complementary tools ('Pair with get_fundamentals and ol_intrinsic_value'). It lacks explicit when-not-to-use guidance or a stated alternative for pure screening, so it stops short of a 5.

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