Get Richgo stock detail

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

No annotations provided, so description carries the burden. It states 'public' and lists content categories, implying a read-only fetch with typical stock data. However, it does not disclose rate limits, authorization needs, or any edge cases (e.g., what happens for invalid tickers). It adds some context beyond the schema but is not exhaustive.

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?

Single sentence that efficiently conveys the tool's purpose and output contents. No redundant words or information.

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 no output schema and no annotations, the description provides a reasonable overview of the returned data. It lists several categories (valuation, cash flow, safety, percentiles, reports) but omits any mention of error handling, pagination, or response structure. For a simple fetch tool with two parameters, this is nearly complete.

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%, with both parameters described adequately (ticker pattern and example, compact as boolean). The description does not add new meaning beyond the schema; it simply states the tool fetches detail. So baseline 3 is 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 uses specific verb 'Fetch' and resource 'Richgo Finance detail', listing included data categories (valuation, cash flow, safety, percentiles, reports). Among siblings like richgo_analyze_stock and richgo_get_scores, this definition clearly distinguishes by the scope of data returned.

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?

No explicit guidance on when to use this tool versus alternatives. With multiple sibling tools (e.g., richgo_analyze_stock, richgo_get_scores), the description does not indicate when to choose this over others or mention conditions to avoid.

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