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

No annotations exist, so the description carries the full behavioral burden. It does add genuinely useful context beyond the schema: the $0.01 USDC-on-Base price via x402 and the exact payment key location (params._meta['x402/payment']) and HTTP endpoint. However, it says nothing about read-only semantics, rate limits, error behavior, or what the response looks like.

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?

The capability list is front-loaded but reads as a run-on enumeration cramming profile, filings, XBRL, and full-text search into one clause. Pricing and HTTP details are useful since they have no structured home, but the whole thing is dense and the trailing truncation suggests padding.

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 four-parameter, multi-mode tool with no output schema and no annotations, the description should clarify how callers switch between profile, filings, and XBRL modes and what each returns. It never explains the mode-selection logic or return shape, leaving meaningful gaps for what is effectively several tools in one.

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 description coverage is 100%, so all four parameters are documented in the schema, establishing a baseline of 3. The description gives a few tag aliases (revenue, net income, assets) that echo the schema's own examples, adding only marginal value and no interaction semantics between `q` and `tag`.

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 description names a resource (SEC EDGAR data) and enumerates three capabilities (company profile, filings, XBRL history, full-text search), so the surface area is visible. But it bundles multiple distinct operations into one tool without indicating which parameter selects which mode, and it overlaps heavily with siblings named edgar__company, edgar__search, and edgar__resolve without distinguishing itself from them.

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 statement of when to use this tool versus edgar__company, edgar__search, edgar__resolve, or company_facts__lookup, all of which appear to cover adjacent ground. The reader is left to infer that supplying a `tag` triggers XBRL history while omitting it produces a profile, but that is never stated.

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