analyze_cash_flow_quality

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

With no annotations, the description carries the burden, and it does disclose meaningful behavioral traits: it operates on 'available annual history', computes specific ratios, and explicitly says it 'flags, it doesn't score or accuse' to set expectations. It does not state what happens with insufficient data, but the scope and interpretive stance are reasonably transparent.

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 core method, scope, caveat, and parameter format are packed into two tight sentences with no filler. The action verb and resource are front-loaded. Every part of the description earns 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?

For a one-parameter analytical tool with an output schema, the description supplies the methodology, scope, and input format needed to call it correctly. The main missing piece is routing guidance relative to the many sibling analysis tools, plus explicit behavior on insufficient history. It is otherwise complete enough.

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 only declares a required string 'symbol' with 0% description coverage. The description compensates by defining the parameter as a ticker and providing concrete formats for NSE and BSE: 'RELIANCE', 'TCS.NS', or 'TCS.BO'. This is exactly the format guidance an agent needs to invoke the tool correctly.

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 states a clear verb and resource: 'Assess cash-flow quality for an NSE/BSE-listed Indian equity across its available annual history.' It also lists specific metrics (cash conversion, receivables/inventory growth vs. revenue), making the tool's scope concrete. It does not explicitly contrast itself with sibling tools like detect_earnings_quality, so it falls short of full sibling differentiation.

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 guidance on when to prefer this tool over related siblings such as detect_earnings_quality, detect_accounting_red_flags, or calculate_financial_ratios. No exclusion criteria or alternative-selection hints are provided. The 'flags, it doesn't score or accuse' remark is interpretive guidance, not usage-selection guidance.

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