Lookup Accession Number

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

Discloses two possible return states (full metadata vs basic with isInDatabase flag) and format flexibility. Consistent with readOnlyHint annotation, no contradictions.

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?

Efficient three-sentence description with clear front-loading of purpose, followed by format and behavior details. No redundant text.

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?

Adequately covers input, output behavior, and edge case (not in database) for a simple lookup tool with one parameter.

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 covers parameter fully (100% coverage), but description adds value by providing format examples and clarifying the two accepted formats.

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?

Description clearly states the tool looks up a filing/exhibit by SEC accession number, with examples of formats. Distinguishes from sibling tools that use different identifiers for filing-related operations.

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?

Provides guidance on input format support and expected return behavior (local vs EDGAR), but does not explicitly contrast with alternative tools like search_sec_filings.

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