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

The description discloses behavioral traits well beyond annotations: fans out in a parallel call, uses fallback order (GDELT→GNews), and notes the USPTO/PatentsView soft-fail after May 2025. It also states the output shape (changes[], total_changes, citation URIs). This is rich transparency and does not contradict the readOnly/openWorld/idempotent annotations.

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 dense but well-organized: it opens with user-intent examples, states the core parallel-feed behavior, explains source-specific fallbacks, documents input formats, summarizes output, and closes with an alternative. Every sentence earns its place and there is no filler or redundancy.

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?

Given the tool has no output schema, the description fully compensates by listing the return structure (changes[] grouped by source, total_changes, pipeworx:// URIs). It also covers all three parameters, source behavior, time-window formats, fallbacks, and the main alternative. This is complete for a tool of this complexity.

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 repeats the schema's `since` semantics (ISO or relative shorthand) and the `value` examples (ticker or CIK), but adds no new meaning beyond what the input schema already documents. It does include a typical-monitoring suggestion ('30d' or '1m'), but that is also present in the schema's `since` description.

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 identifies this as a change-feed tool for a company over a date window, with concrete natural-language examples ('What's new with X', 'updates on Acme'). It distinguishes itself by naming entity_profile as the alternative for static profiles, and the fan-out to SEC, GDELT/GNews, and USPTO makes the scope 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 when-to-use guidance via query patterns and an explicit alternative: 'Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.' This is a clear when/alternative distinction, and it explains the fallback behavior (GDELT preferred, GNews on rate-limit/5xx), which helps with trust.

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