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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds the authoritative data source ('official SEC company dataset') and timing context, but says nothing about miss behavior (unresolvable identifiers) or ambiguous matches, which is the main behavioral risk for a resolution tool.

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 sentences that each earn their place: the first defines the operation and its source of truth, the second gives the trigger condition. Front-loaded and free of padding.

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 read tool with rich annotations, the description is nearly sufficient, but with no output schema it leaves the return value undefined — an agent cannot tell whether resolution yields a CIK, canonical name, match list, or failure signal. That gap matters for a tool whose output feeds downstream research.

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 string parameter is fully documented, so the baseline of 3 applies. The description's mention of 'ticker, CIK, or exact company name' merely restates the schema's own parameter description ('Ticker, CIK, or exact SEC company name') without adding format, casing, or matching-precedence detail.

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 ('Resolve') and enumerates the accepted resource forms (ticker, CIK, exact company name) against the 'official SEC company dataset', which is concrete and unambiguous. No sibling in the filedproof set performs issuer identity resolution, so the tool is implicitly distinct, but the description never names or excludes an alternative, keeping it short of a 5.

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?

'Use this before research when issuer identity is uncertain' gives an explicit trigger condition and sequencing guidance relative to downstream tools. It stops short of stating when NOT to use it (e.g., when the CIK is already known) or naming an alternative lookup path.

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