red_flags

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that the checks are fixed and evidence-backed, but it does not explain data sources, limitations, or what happens with incomplete reported numbers.

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 description is front-loaded with the core purpose and uses a compact enumerated list of checks. It is dense but efficient, with little wasted text, though the list format makes it slightly run-on.

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?

The description explains the twelve checks and says each comes with evidence, which is useful for a read-only analysis tool. However, with no output schema, it does not describe the return structure or evidence format, and it leaves the required symbol input undefined.

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 schema has 0% description coverage and the description never mentions the required symbol parameter. The parameter name 'symbol' is somewhat self-explanatory, but the description adds no format, exchange, or identifier semantics to compensate for the schema gap.

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 clearly states that this tool runs twelve fixed checks on reported numbers and enumerates the checks, which distinguishes it from generic financial data tools. It does not explicitly contrast itself with siblings such as company_overview or financial_statement, but the purpose is still specific and identifiable.

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 explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The agent can infer it is for red-flag screening, but the description does not name siblings or conditions for selecting it.

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