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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates this is a read/retrieve operation, but does not mention response format, pagination, error handling, rate limits, or any special requirements. The phrase 'full range of company data' is vague and fails to provide actionable detail beyond what the name itself implies.

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 concise at two sentences and front-loads the core purpose. However, the second sentence contains some redundancy ('This API allows users to search...') and vague phrasing ('and much more') that could be tightened. It earns a 4 for overall efficiency and clarity.

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?

The tool has only one parameter and no output schema, so the description must convey what the response contains. It lists some example fields (stock price, market cap, industry) but does not guarantee completeness or describe the response structure. It also does not address edge cases like unknown CIKs. This is adequate but lacks full context.

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 schema's parameter description is minimal ('CIK number'), but the tool description adds meaningful context by explaining that CIK is the Central Index Key and how it is used to search for companies. This helps the agent understand the parameter's purpose and format beyond the schema, despite the high schema coverage (100%).

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's function with a specific verb: 'Retrieve detailed company profile data by CIK'. It explicitly identifies the resource (company profile) and the unique identifier (CIK), distinguishing it from sibling tools like getCompanyProfile that likely use symbols. The inclusion of example data fields adds specificity.

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 provides clear context for when to use this tool: when you have a CIK identifier and need a company profile. It says 'This API allows users to search for companies using their unique CIK identifier'. However, it does not explicitly mention alternatives or when not to use it, so it falls short of a 5.

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