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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, and the description still adds real semantic context: common-horizon readiness applies to the dated review, newer individual observations can exist, and unavailable/mismatched/stale captures never imply a passing review. The disclaimer that this is captured research evidence rather than a trade recommendation or backtest further constrains how the output should be treated.

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?

It is front-loaded with the core action and stays to a handful of dense sentences, each carrying substantive caveats. The mid-sentence field-name list is slightly opaque, but no sentence is filler.

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 for a zero-argument read tool it covers semantics, readiness caveats, and the non-recommendation disclaimer well. The one real gap is sibling disambiguation against financial_evidence_review.

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, which is the baseline-4 case, and the description correctly spends no effort explaining nonexistent inputs. The named fields (review_asof, review_scope, etc.) are output-side concepts, not parameters, so nothing is owed here.

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 gives a specific verb and resource: 'Read a dated USD funding review and its nine inputs,' which tells an agent exactly what is returned. It does not, however, differentiate this tool from the very similar sibling 'financial_evidence_review', leaving an agent to guess which review tool to call.

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 offers interpretation guidance ('inspect review_asof, review_scope, latest_per_instrument and newer_observation_available before ready, issues and capture age') but never states when to choose this tool over financial_evidence_review, financial_evidence_packet, or financial_evidence_route. No preconditions or exclusions are given, so selection must be inferred.

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