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

Annotations cover read-only and open-world semantics, and the description adds genuinely useful context beyond them: the x402 pricing model ($0.01 per successful call on eip155:8453) and the 5-call/day free tier across all tools. That cost/limit disclosure is behavior an agent needs and cannot get from the schema. It stops short of stating auth or error handling.

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 establishes the resource and its contents, with the pricing constraint placed second. The field enumeration is long but earns its place by defining the return surface in the absence of an output schema.

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 description usefully enumerates the returned data and discloses pricing/quotas. The one gap is that both parameters are optional (required: 0) yet at least one of ticker or cik must logically be supplied, and the description never states that constraint.

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% and both parameters carry their own descriptions, including the CIK-as-alternative-to-ticker relationship, so the schema does the heavy lifting. The description adds no parameter syntax or format detail beyond it, making the baseline 3 correct.

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 the specific resource (company profile and key fundamentals), the source (SEC EDGAR XBRL data), and enumerates the data set, which cleanly separates it from siblings like sec_filings and sec_insider_trades. An agent can identify exactly what this tool returns without opening the schema.

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?

Usage is implied by the enumerated data set (use this when you need fundamentals rather than filings or insider trades), but there is no explicit when-to-use/when-not statement or a named alternative for adjacent needs. Adequate but leaves routing to inference.

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