Get company fundamentals history

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

Annotations already declare read-only, idempotent, non-destructive. Description adds valuable behavioral context: requires PRO plan, data sourced from SEC filings. No contradictions.

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?

Two compact sentences: first defines purpose and output, second provides usage guidance and requirement. No fluff, front-loaded with key 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, description lists key metrics returned, which is sufficient for an agent to understand the output. Also mentions PRO plan constraint. Lacks detail on data structure (e.g., array shape) but tone is adequate.

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 covers all 3 parameters with descriptions. Description adds meaning by enumerating example output fields (revenue, net income, etc.), which helps infer return value beyond the 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?

Description clearly states it returns historical company fundamentals derived from SEC filings, listing specific metrics. Distinguishes from sibling tool edgaralert_get_company_profile by noting it is for multi-year history versus a latest snapshot.

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 says when to use this tool (need historical fundamentals) and when not to (need latest snapshot), recommending the alternative edgaralert_get_company_profile. Also mentions the PRO plan requirement.

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