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

Annotations already carry the full safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the bar is lower. However, the description adds zero behavioral context beyond that — it discloses nothing about return format, failure modes, or what the agent should expect. It contributes nothing where the get_calls calibration example added scoping context and earned a 3.

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 two words long, but this is under-specification, not deliberate conciseness. It contains zero informative content and fails to use its space to state scope, behavior, or parameter context.

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 no output schema, the description carries the burden of explaining what the tool returns, and it says nothing at all. An agent cannot determine what a receipt represents, when the call succeeds, or how this differs from job_status — completely inadequate even for a one-parameter tool.

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%, and the description must compensate per the rubric. 'PrivateDAO get_receipt' adds no meaning for receipt_id — it doesn't explain what a receipt_id is, where to obtain one, or how it relates to the siblings. Only the JSON Schema pattern '^rvr_[A-Za-z0-9]+$' hints at format, which the schema already provides.

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?

Tautological: description restates name/title.

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?

There is no guidance whatsoever about when to call this tool versus siblings like job_status or verify_basic, which could plausibly overlap as status/record-lookup tools. The description is empty rather than misleading, so it earns the 'no guidance' score.

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