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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value by stating 'Returns every filing on record' (comprehensive behavior) and 'No API key required' (auth requirement), which are useful disclosures beyond the structured metadata. It does not mention pagination or rate limits, but given annotation coverage, a 4 is appropriate.

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 compact and front-loaded: the core action and return type come first, followed by bulleted use cases and a source note. No sentence is wasted, and the structure makes it easy for an agent to quickly grasp the tool's purpose and applicability.

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?

Given the tool has a single main parameter (CIK), an output schema exists, and annotations cover safety, the description is largely complete: it explains what is returned, how to find CIK, and that no API key is needed. The main omission is lack of detail on pagination or large result set handling, which could matter for 'every filing on record', but the output schema likely covers return structure. A 4 reflects this minor gap.

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 0%, so the description must compensate for parameter details. The description only mentions CIK in passing, while the input schema contains several other parameters (wholesaler_ids, source_resource_id, etc.) that are entirely unaddressed. The CIK-specific detail in the schema (zero-padding, example) is not supplemented by the description. This is a clear gap.

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 opens with a specific verb and resource: 'Retrieve all SEC filings for a company or institution using its CIK.' It explicitly names the returned fields (form type, date, accession number, description) and frames the scope as 'all filings', which distinguishes it from siblings like SearchEdgar13F. The title and description align perfectly.

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 'Use this tool when' bullet list gives concrete conditions: having a CIK, wanting full filing activity, tracking 13F/ADV/ownership history, and needing accession numbers. It provides clear context, but stops short of explicitly naming alternatives like SearchEdgar13F or stating when not to use this tool. Thus it earns a 4 rather than a 5.

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