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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds the useful fact that the result resolves to a CIK, but says nothing about rate limits, throttling, or how EDGAR matching behaves with ambiguous names.

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 sentence with zero filler, front-loaded with the domain (SEC EDGAR) and the core input->output contract. Nothing needs to be trimmed.

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 2-parameter search tool with an output schema and read-only annotations, the description covers the essentials. The only real gap is the undocumented 'limit' parameter and the absence of any usage routing, which keeps it short of a 5.

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 0%, so the description must compensate. It clarifies that 'q' accepts a ticker or a company name, which is genuinely beyond the bare 'q: string' schema, but the 'limit' parameter is left entirely undocumented in both schema and description.

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 verb and resource ('SEC EDGAR company search') and even the input->output mapping (ticker or name -> CIK), which lets an agent distinguish it from lookup siblings like sec_filing or sec_financials. It does not, however, explicitly name the closest siblings (sec_company_intelligence, sec_company_submissions), so a 5 is not warranted.

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?

The description only says what the tool does; it gives no when-to-use context, no prerequisites, and no routing advice versus alternatives such as sec_full_text_search or sec_company_submissions. An agent must infer all usage conditions.

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