solvency

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds context beyond that: it clarifies that tickers are required, explains quarterly toggle, and lists all supported indicators. It also states 'pre-computed' and recommends using it over raw statements, which conveys the tool's derived nature. No contradictions with 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 description is front-loaded with the purpose and usage guidance, then lists the available indicators. The indicator list is somewhat redundant with the schema enum but still useful for quick scanning. It is concise overall, though the final list sentence is long. No wasted prose.

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 13 parameters and a full schema plus output schema, the description covers the essential context: what the tool does, when to use it, and key usage constraints. It does not explain return formats, but the output schema exists. The description is sufficiently complete for an agent to invoke the tool correctly, especially with the indicator list and example.

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?

Schema description coverage is 100%, so the baseline is 3. The description reinforces tickers as a requirement and names quarterly/start_date/end_date, but these are already well-documented in the schema. The indicator list duplicates the enum. The description adds minimal new semantic value beyond the schema, though it does give a concrete example (tickers='AAPL').

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 the tool provides pre-computed solvency ratios (debt-to-equity, interest coverage, debt-to-assets, net debt to EBITDA), giving a specific verb+resource and distinguishing it from sibling tools like liquidity or profitability. It also lists the exact available indicators, leaving no ambiguity about its scope.

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?

The description explicitly says 'Use instead of raw financial statements', providing a clear when-to-use recommendation. It also gives an example requirement (tickers='AAPL') and mentions quarterly flag and date range support. However, it does not explicitly state when not to use it or mention alternatives like liquidity for other ratio types.

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