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

With no annotations, the description carries full behavioral burden. It discloses the data range and premium ('PRO') nature but omits read-only status, authentication requirements beyond the schema, rate limits, error behavior, and return structure.

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 compact, front-loaded sentence fragment with no wasted words. 'PRO.' is slightly cryptic but likely signals subscription access, and the core data scope is stated immediately.

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 simple retrieval tool with no output schema and no annotations, the description covers the data scope and metrics but leaves gaps around return format, authentication behavior, and sibling differentiation. It is minimally sufficient to guide invocation but not rich.

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 67%. The description adds useful meaning to the period parameter by stating maximum annual and quarterly periods, but does not explain the required company parameter or access_token beyond what the schema already says.

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 indicates historical financial data by listing metrics and time ranges (10 years annual or 12 quarters). It lacks an explicit verb and does not differentiate from siblings like key_financials or compare, but the resource is understandable.

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 guidance on when to use this tool versus alternatives such as key_financials or compare. The only contextual hint is 'PRO,' which suggests a subscription tier but not usage conditions.

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