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

Despite annotations already indicating read-only, open-world, and idempotent behavior, the description adds substantial non-obvious details: parallel fan-out across sources, GDELT-to-GNews fallback on rate limits/5xx, USPTO PatentsView sunset soft-failure, and the exact return shape (changes[], total_changes, pipeworx:// URIs). This goes well beyond annotation-only transparency.

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 long but every clause earns its place: it front-loads user intent examples, explains the fan-out architecture, documents fallback behavior and failure modes, and ends with a clear alternative. The dense but structured flow keeps it scannable despite its length.

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?

Even without an output schema, the description fully specifies return contents (structured changes[] grouped by source, total_changes count, citation URIs), input formats, and edge-case behavior (USPTO soft-fail). It covers all necessary operational context for an agent to invoke 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%, so the baseline is 3. The description largely repeats what the schema already says for each parameter, but adds a minor usage recommendation ('Use "30d" or "1m" for typical monitoring') that slightly enhances the `since` semantics without introducing new meaning for `type` or `value`.

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 opens with concrete user phrasings and defines the tool as a change feed for companies over a date window, clearly distinct from sibling tools. It names the exact data sources (SEC EDGAR, GDELT/GNews, USPTO) and explicitly contrasts with entity_profile, making the purpose unmistakable.

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 gives explicit usage context: when users ask for "what's new" or "latest updates" in a time window, this tool is appropriate. It also provides a direct alternative: "Use entity_profile instead when you want the static profile... regardless of window," and recommends typical monitoring windows like '30d' or '1m'.

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