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

With no annotations, the description carries the full behavioral burden; listing the returned fields gives useful insight into the response shape. However, it never states that this is a read-only lookup, nor mentions error behavior for an unknown ticker/CIK, so disclosure is partial.

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 compact sentence with zero padding and the resource named first. The only weakness is the verbless noun-phrase style, which slightly reduces front-loaded actionability.

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 one-parameter lookup, the description adequately signals the returned content in place of an output schema. It is still thin on routing context and behavioral caveats, leaving gaps an agent must fill from siblings' names alone.

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% and the single 'cik' parameter already documents that it accepts a ticker or CIK. The description adds no syntax or format detail beyond the schema, which matches the baseline 3 for a fully documented parameter.

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 resource (EDGAR entity profile) and enumerates the data it exposes (name, SIC, addresses, fiscal year end, former names), which distinguishes it from siblings like company_facts or directors. It lacks an explicit verb such as 'retrieve', so the agent must infer that this fetches rather than writes.

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 versus alternatives such as company_facts, directors, or subsidiaries, and no mention of lookup-by-CIK prerequisites. Usage is only implied by the fields listed.

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