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 is covered. The description adds no further behavior—no auth requirements, rate limits, data freshness, or scope—leaving the burden on the annotations alone.

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?

It is a single short fragment, but brevity here reflects under-specification rather than efficient conciseness—there is nothing front-loaded because there is essentially no 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?

An output schema exists, so return values need not be described, but for an 8-parameter tool with 0% param coverage, zero usage guidance, and no behavioral context, the description is far too thin to invoke the tool correctly.

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?

Eight parameters (ats, cik, site, enrich, tenant, ticker, datacenter, careers_slug) have 0% schema description coverage, and the description explains none of them. Cryptic names like 'ats', 'enrich', and 'careers_slug' are entirely uninterpretable without help, and nothing is compensated here.

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 phrase 'SEC EDGAR company 360 overview' names the resource (SEC EDGAR company) but '360 overview' is marketing filler that does not state a verb or what data is actually returned. With many close siblings (sec_company_search, sec_company_submissions, sec_financials, sec_insider) the agent cannot tell what this 'intelligence' tool uniquely provides.

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 when-to-use, when-not-to-use, or alternative guidance. Given the dense cluster of sec_* siblings, the description should route the agent among them but offers nothing.

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