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

With only readOnlyHint=true in annotations, the description carries real behavioral detail: hard cap of 20 matches, return shape {results, count}, null fields are OMITTED so cik cannot be assumed present, matching is literal substring, and tickerStatus must be checked before treating a match as live. That is exactly the context annotations do not provide.

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?

Front-loaded with the core action, then the return shape, then the caveats; every clause is operational (cap, omitted nulls, substring matching, downstream calls). It is dense and slightly packed, but nothing reads as filler.

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?

No output schema exists, yet the description specifies the return shape, the field set, the hard cap, and the null-omission rule, plus the resolution caveats and next-step tools. An agent has everything needed to call it and interpret results correctly.

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 coverage is 100% (baseline 3), but the description adds matching semantics the schema omits: literal substring on ticker/companyName, class-share punctuation handling, and a digit-only CIK path. It notably does not echo the schema's 'industry' mention, adding useful precision about what actually matches.

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?

States a specific verb+resource: 'Resolve a company name, ticker or CIK to its SEC identity.' It positions itself as the identity-resolution entry point among many sibling search/get tools and names the downstream siblings (get_fundamentals, get_business_summary), so an agent can distinguish it from get_* data tools without opening schemas.

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?

Clear routing: 'Once resolved, call get_fundamentals or get_business_summary' tells the agent this is a precursor step. It also warns former names/misspellings do NOT resolve. There is no explicit when-not or statement of which query form to prefer, so it stops 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.