get_latest_issue

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

With no annotations, the description carries the full disclosure burden and does well: it names the exact price and chain, the funding source (the server's configured wallet), an optional preflight gate, and the artifacts produced (issue, receipt, settlement transaction, ledger hash check). It stops short of stating what happens when payment or preflight fails, which for a pay-per-call tool is the main remaining unknown.

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?

One sentence, front-loaded with the resource being fetched, with cost and return details following in priority order. It runs on and the dangling 'optionally checked first by Agent Trust preflight' clause is grammatically loose, but no sentence is padding.

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?

An output schema exists, so return-shape explanation is optional, and the description still sketches the four returned artifacts. Given a paid, single-purpose fetch, the payment model, funding source and optional trust check are covered; failure and retry semantics are the notable omission.

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?

Zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly adds no parameter detail, since the schema takes no input.

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?

States a concrete resource — 'Today's Regime Feed issue' — which pairs with the verb 'get' from the name and makes the recency scope explicit. The word 'Today's' implicitly separates it from get_delayed_issue, but no sibling is named outright.

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 supplies an important usage condition — this is a paid call (0.10 USDC) and can be gated by Agent Trust preflight — which tells the agent to expect a cost and a possible check step. It never says when to prefer this over get_delayed_issue or list_issues, so routing among the eight siblings is left to inference.

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