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

No annotations are provided, so the description carries the full burden. It says 'Retrieve,' which implies a read-only operation, but it does not disclose parameter handling, required input combinations, return format, or any rate limits. The behavioral transparency is minimal.

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 description is a single concise sentence that front-loads the purpose and lists the key data categories. The reference to 'FMP SEC Company Full Profile API' adds some verbosity but also provides source context, so it earns its place.

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 and no annotations, the description needs to cover functional context. It lists the types of data returned, which is helpful, but it omits parameter requirements and does not clarify what happens if both cik and symbol are provided. This leaves the tool slightly incomplete for a profile endpoint with optional parameters.

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?

The input schema already provides full descriptions for both parameters (cik and symbol) at 100% coverage, so the baseline is 3. However, the description adds no additional meaning about how these parameters are used or whether at least one is required, which is a missed opportunity given both are marked optional.

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 clearly states the tool retrieves detailed company profiles and lists specific content areas (business descriptions, executive details, contact info, financial data). However, it does not explicitly distinguish itself from sibling tools like getCompanyProfile or getCompanyProfileByCIK, relying on the name to hint at the SEC-specific context.

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 gives no explicit guidance on when to use this tool versus alternatives such as getCompanyProfile or getCompanyProfileByCIK. It implies use when detailed profile data is needed, but there is no mention of prerequisites, exclusions, or how to choose between cik and symbol.

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