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

With no annotations, the description carries the full burden. It usefully discloses the quote expiry (~30 minutes) and the environment/config dependency, which the agent could not infer elsewhere. But it omits what happens after expiry, whether repeated calls reuse or replace a lock, and whether the quote is a price or a signed payload.

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 action and its duration up front and the configuration prerequisite after. No filler, no repetition of the title.

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?

For a tool with zero annotation coverage, 0% schema descriptions, and no output schema, the description is too thin. It does not say what the quote result contains or how the two optional inputs combine, which is exactly what the absent structured data would otherwise supply.

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 description coverage is 0%, so the description must explain both parameters, yet it only hints that USD is the input side of the conversion. It never clarifies what "micronoid" is (an amount string? a token id?), nor that both parameters are optional, leaving the either/or input ambiguity unresolved.

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?

Uses a specific verb ("lock") plus the resource (a USD→μNOID quote) and the lock duration, so the agent knows exactly what action is performed and on what. It is distinguishable from siblings like list_pricing or create_invoice, though it never names an alternative.

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 a prerequisite ("Requires NOID_USD_RATE or PRICE_FEED_URL") and a negative condition ("not explorer premium"), which implies when the tool will work. However, it never states when to use this rather than list_pricing or create_invoice, nor the workflow position (e.g., call before creating an invoice).

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