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

Annotations cover readOnlyHint=true and openWorldHint=true, so the safety profile is declarative. The description adds that results are SEC EDGAR records with CIKs, but says nothing about output shape, pagination or resolution behavior (e.g., fuzzy name matching returning multiple CIKs). Since an output schema exists, less is required, but the resolution-specific behavior is the key unknown left unaddressed.

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?

Two tight sentences, purpose first then routing. No filler; could arguably mention the CIK output format more concretely, but it wastes nothing.

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 a 100%-covered 2-param schema, annotations and an output schema, the description gives the purpose and the two sibling alternatives that an agent needs. The remaining gap is behavioral (how a name query resolves to possibly multiple CIKs), which is minor given the structured data present.

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 both params are documented there ('Ticker symbol or company name', 'Max matches, default 10, max 100'). The description adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

Specific verb+resource: 'Resolve a ticker or company-name query to SEC EDGAR company records with CIKs.' It states both the input (ticker/name query) and the output (company records with CIKs), which is the exact disambiguation needed.

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?

Explicitly names two alternatives and their conditions: sec_company_submissions for one company's filing history, datasets_sec_companies_search for stored company and financial records. An agent can route without opening schemas.

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