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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful behavioral detail beyond annotations: the filtering thresholds, default horizon, time sorting, and the contents of each row including settlement-window statistics.

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 front-loaded and dense with useful detail. Every part earns its place by specifying the filter criteria, sorting behavior, default horizon, and the statistics included in each row.

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 read-only annotation, full schema coverage, and output schema, the description is largely complete for correct invocation. It could be stronger with explicit sibling differentiation, but the filtering and returned-row details cover the main gaps.

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 both parameters are already well documented. The description adds only the default horizon of 4 hours, which is already present in the schema, and does not mention the lang parameter or add further semantic nuance.

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 states a specific resource (funding settlements) and scope (upcoming in the next hours), including thresholds, sorting, and returned statistics. It is clear what the tool returns, but it does not explicitly differentiate itself from sibling tools such as funding_events or funding_history.

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?

Usage is implied by 'coming in the next hours' and the notable-filter criteria, which suggest this is for upcoming notable settlements rather than historical or general event browsing. However, there is no explicit when-to-use guidance or named alternative among the sibling tools.

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