Get Richgo score ranking

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

With no annotations, the description fully carries the burden of disclosing behavioral traits. It only states 'Fetch,' implying a read operation, but does not mention authentication needs, rate limits, pagination, or the impact of the limit parameter on behavior. This is minimal for a tool that retrieves data.

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 a single sentence that front-loads the action and resource, listing all optional filter types. Every word contributes without redundancy, making it highly concise and easy to parse.

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 the presence of 5 optional parameters, no output schema, and no annotations, the description provides the basic purpose but lacks details about return format, error handling, or limitations. It is sufficient for a simple fetch but incomplete for an agent to fully understand the tool's behavior.

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?

The input schema already provides descriptions for 3 of 5 parameters (sort, tier, period) and enumerates market options. The description merely lists parameter names without adding new semantic detail. Given 60% schema coverage, the description does not need to compensate much, but it could clarify default behaviors or valid values more explicitly.

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 fetches the Richgo score/screener table with optional filters. While it is specific about the resource (score/screener table), it does not explicitly distinguish from sibling tools like richgo_get_ai_rankings or richgo_get_breakout, which serve different data types.

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 guidance is provided on when to use this tool versus alternatives. There is no discussion of context, prerequisites, or exclusions, leaving the agent without decision support for selecting among siblings.

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