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

The annotation readOnlyHint=true already indicates no side effects. The description adds that metrics are computed from 'existing financial statements', implying no new data creation or modification. It lists the specific metrics computed, providing insight into the return content beyond the annotation.

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 concise and front-loaded, with the primary purpose in the first sentence. Every sentence contributes value: the first states the overall function and the second lists key metrics. No unnecessary words or repetition.

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?

Given four well-documented parameters, no output schema, and readOnly annotation, the description covers the tool's purpose and what it computes. It could be more complete by specifying output format (e.g., table or JSON) or data prerequisites (e.g., financial statements must exist). However, the 'existing financial statements' hint partially addresses this.

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%, with detailed descriptions for each parameter (e.g., ticker includes format guidance and fallback instructions). The tool description adds no additional parameter semantics beyond what the schema already provides. Baseline 3 is appropriate as the description does not enhance parameter understanding.

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 action ('Compute'), the resource ('annual quality, moat, earnings-quality, and capital-allocation metrics'), and the scope ('for one exact Bullrun ticker from existing financial statements'). It lists specific metrics (ROIC, ROE/ROA, etc.), which distinguishes it from sibling tools like get_financial_history or get_stock_metrics. The 'Read-only' tag aligns with the annotation.

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 implies usage for computing quality and moat metrics from existing financial statements but does not explicitly state when to use this tool versus alternatives such as get_financial_history or get_forward_estimates. No when-not-to-use scenarios or preconditions are mentioned.

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