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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile and external-data nature are covered. The description adds value by enumerating the returned attributes, which is real context beyond the annotations. It stops short of noting EDGAR lookup/rate behavior, resolution of ticker-to-CIK, or what happens when a company is not found.

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?

A single front-loaded sentence identifying source and payload with zero filler. Every clause earns its place by naming a distinct returned field.

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?

With no output schema, the field enumeration effectively stands in for a return-value description, which is the right call for this tool. Missing is the dual-key behavior (both params optional, so what happens with none/conflicting) and failure handling, the only meaningful gap.

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 100% with both parameters documented and exemplified (cik '320193', ticker 'AAPL'). The description adds nothing about how the two keys interact or which takes precedence, so baseline 3 is appropriate.

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?

States a specific resource and source ('Company profile from SEC EDGAR') and enumerates the fields it returns (SIC industry, incorporation state, fiscal year end, addresses, exchanges, former names). An agent knows exactly what data it gets. It does not differentiate itself from siblings like sec_company_search or sec_company_financials, which costs it the top score.

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 call this versus sec_company_search (for discovering a CIK) or sec_company_filings/financials. Nothing says whether cik or ticker is preferred, or what happens if neither is supplied (both are optional). The agent must infer usage entirely.

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