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

Annotations only declare readOnlyHint=true, but the description discloses a wealth of behavior: metered daily AI quota (25/day, UTC reset, burst limiter), auth requirement and AUTH_REQUIRED failure mode, and a precise return shape. It even warns that `score` is a fused-rank value comparable only within one response, which prevents misuse.

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 key facts (paid, semantic retrieval, ticker-scoped), and each clause carries real information about quota, auth, and return format. It is dense with parentheticals and slightly long, but nearly every sentence earns its place.

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 no output schema, the description fully specifies the response object ({summary, ticker, count, chunks, quota_remaining_today}) and per-chunk fields, plus auth and quota constraints. An agent has everything needed to call and interpret the result 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 description coverage is 100% and every parameter (ticker, query, k) is already documented in the schema, including k's default and hard cap. The description mostly restates this, though it adds the fused-rank meaning of the returned score, which is output rather than parameter semantics. Baseline 3 is appropriate.

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 ('semantic retrieval over EMBEDDED SEC filings for a ticker') and clarifies the input style with a concrete example natural-language question. It is clearly distinguishable from sibling search tools like search_company, search_news_archive, and ol_13f_filer_search.

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?

Explains when to reach for it (a natural-language question over filing text) and gives strong operational context: it is 'the ONE metered tool', needs a signed-in account or API key, and anonymous calls fail AUTH_REQUIRED. It stops short of naming an explicit alternative or a 'when-not-to-use' case, so not quite a 5.

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