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

With no annotations, the description carries the full behavioral burden. It does add genuine value by clarifying that 'n counts periods, not rows' and that rows carry field names and display names, which hints at return contents. It says nothing about auth, rate limits, or how 'latest' is determined, so the disclosure remains thin.

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?

Two compact sentences plus a fragment, front-loaded with the core action and the most error-prone parameter note. Nothing is padded, though the final clause is terse enough to be slightly telegraphic.

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 5-parameter financial tool with no output schema and no annotations, the definition covers parameter mechanics and row contents but omits how it differs from annual/TTM variants and gives no indication of the returned shape or row count relative to periods. Adequate but with clear gaps.

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 coverage is 100%, so the baseline would be 3. The description goes slightly beyond the schema by disambiguating n ('counts periods, not rows') and by stating that field names and display names appear in rows, which is a mapping aid the schema does not provide.

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 ('Get field-level financial rows') with a scope ('up to 20 periods'), so the agent knows it returns statement line items. However, it never distinguishes itself from the siblings get_financials_annual and get_financials_ttm, so the 'latest' positioning is left to inference.

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?

'Use one kind per call' is an invocation constraint, not usage guidance. There is no statement of when to pick this tool over get_financials_annual or get_financials_ttm, nor any prerequisites, so the agent has no routing signal.

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