ORATS Core Data

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

Annotations already include readOnlyHint=true, and the description does not contradict that. It adds context about being 'raw' and 'straight from the data vendor', but does not disclose additional behavioral aspects like rate limits or data freshness. Given the annotations cover the safety profile, this is adequate but not rich.

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 well-structured with an opening summary, a use-case list, and an Args/Returns breakdown. It is longer than minimal but every section earns its place, providing essential information without excessive verbosity.

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 read-only tool with two simple parameters, the description covers the data scope, field selection, and return count. It doesn't mention error handling or rate limits, but those are not critical for this type of tool. The description is sufficiently complete given the sibling context.

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 0%, so the description fully compensates. It explains the 'fields' parameter with three options (specific names, 'all', or empty for curated default) and clarifies 'ticker' as 'Stock symbol'. This adds meaningful semantics beyond the bare schema.

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 retrieves raw ORATS analytics with 340+ fields, and distinguishes it from curated endpoints by saying 'Use when the curated endpoints don't carry the specific field you need.' It also lists specific user requests that map to this tool.

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?

Explicitly provides when-to-use guidance including three bulleted examples ('A specific ORATS field by name', 'Deep vendor-level analytics not in other tools', 'Bulk fundamentals+vol context for one ticker') and references curated endpoints as alternatives, making usage conditions clear.

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