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

With no annotations, the description carries the burden of behavioral disclosure. It mentions optional filters and date format, which is helpful. However, it does not state whether the operation is read-only, requires authentication, or describes the response format. It adds some behavioral context but lacks a full safety/return profile.

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 concise and well-structured: two sentences, first states the core function and filters, second provides usage guidance. Every word earns its place, no redundant information.

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?

The tool has 4 parameters, no output schema, and no annotations. The description covers the purpose, all parameters at a high level, and usage context. It doesn't mention return shape or limitations, but given the simple search nature, it is reasonably complete. Slightly more detail on output would elevate it further.

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. It explains that 'query' is a keyword, 'ticker' is an optional filter, and date range uses YYYY-MM-DD format. This adds meaning beyond the bare schema names, though it doesn't elaborate on date_from/date_to semantics beyond their names.

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 clearly states the tool's function: 'Search across all SEC filings in the database by keyword.' It uses a specific verb (search) and identifies the resource (SEC filings). It also distinguishes itself from siblings by explicitly noting it is for open-ended questions 'rather than looking up one known ticker.'

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 description provides explicit usage guidance: 'Use this for open-ended questions like... rather than looking up one known ticker.' This gives a concrete example and indicates when not to use it, effectively guiding the agent toward the appropriate tool.

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