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

Annotations already establish the safe read-only, idempotent, closed-world profile, so the bar is lower. The description adds genuine substance beyond them: RyuScore is defined as a 0-100 score derived from seven weighted criteria, and the company description is flagged as verbatim from the latest annual report, which tells the agent what the data actually represents.

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?

A single tightly packed sentence that front-loads the return fields and wastes no words. It is list-heavy but every item is information-bearing and 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?

With no output schema, the description carries the full burden of describing return values, and it does enumerate the fields plus explaining RyuScore's derivation. What is missing is only secondary detail like whether the response is a snapshot vs. historical or any note on data freshness.

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% for the single ticker parameter, including a pattern and an example (NVDA or BRK-B), so the schema does the heavy lifting. The description adds nothing about the ticker argument, making the baseline 3 appropriate.

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 enumerates exactly what the tool returns for a given ticker: price, market value, P/E, returns, sector, RyuScore, and the verbatim company self-description. That is a concrete verb+resource with real substance, though it never explicitly contrasts itself with siblings like get_financial_history or get_company_news.

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 statement of when to use this tool versus alternatives such as get_financial_history, get_company_news, or search_stocks. Usage is only inferable from the field list, so an agent must guess at the routing decision among the five siblings.

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