company_overview

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

No annotations provided; description only mentions output includes overview and recent SEC filings. Does not disclose error handling, rate limits, or side effects of input.

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 concise sentences plus two code examples. No wasted words. Front-loaded with purpose.

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?

No output schema and only partial param description. Does not explain what fields the overview contains or how SEC filings are presented. Incomplete for effective use.

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 identifier meaning but filingLimit lacks description. Description does not explain filingLimit beyond schema. 50% schema coverage but description adds no param info.

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?

Clear verb 'Get' and resource 'comprehensive overview of a public company'. Distinguishes from siblings like company_financials and company_ratios. Examples solidify understanding.

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?

Labels itself as 'ideal starting point' but no explicit when-not-to-use or comparison to alternatives. Advises starting point but lacks exclusion criteria.

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