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

No annotations are provided, so the description carries the full behavioral burden. It discloses the schema's scope (sources, tolerance basis, value timing), which is useful, but never states that this is a non-mutating read, whether the contract is versioned or static, or whether the result is cached. Adequate but leaves the safety profile to inference from the 'get_' name.

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?

Two short sentences with the content summary front-loaded and the usage directive second. Nothing is wasted, though the opening fragment is slightly elliptical and could read as a headline rather than a complete statement of purpose.

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 an output schema present, the description needn't explain return values, and with zero parameters there is nothing to document. It tells the agent what the contract governs and when to consult it, which is nearly everything a caller needs; only the read-only/versioning behavior is unstated.

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?

The tool takes zero parameters, so the baseline is 4. The description adds no parameter information because none is needed; the empty schema is self-explanatory.

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 names the resource ('the settlement contract') and enumerates its content precisely: which sources count, what the tolerance is relative to, and when the value is taken. The implied verb is a read of a reference document, which is clear enough, though the domain term 'settlement' is jargon that is never grounded. Sibling tools (events, leaderboards, feeds) are in a distinct domain, so differentiation is implicit.

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 second sentence gives an explicit trigger: 'Read this before describing how anything on this platform gets settled.' That tells the agent when to reach for it. There are no named alternatives or when-not conditions, but for a parameterless reference tool the context is sufficient.

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