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

With no annotations, the description carries the full burden. It transparently explains the semantics of the threshold, the context of micro-payment settlement mode, and how it differs from the safety-net sweep. It also discloses whether the value is an agent override or platform default. No side effects or hidden behaviors are relevant, and nothing is misleading.

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 sentences, front-loaded with the main action ('Returns your threshold'), then concise explanatory details. Every word adds value; no redundancy or fluff. The structure is efficient and clear.

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?

The tool is simple (0 params, no output schema, no annotations), and the description provides sufficient context: what is returned, what it means, and how it relates to the broader payment system. It could mention return format or error conditions, but for a getter of this simplicity, the description is adequately complete.

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 has zero parameters, so the schema trivially covers all parameters (100%). The description adds no parameter details, but none are needed. Per the rubric, a baseline of 4 is appropriate for zero parameters.

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 clearly states the tool returns the calling agent's micro-payment settlement threshold, explains what that means (accrued debt amount for immediate settlement), and distinguishes it from sibling tools like wallet_set_autopay_threshold. It is specific about the resource and the verb 'Returns', with full differentiation.

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?

Usage is implied rather than explicitly guided. The description conveys this is a read-only inspection tool for the autopay threshold, and the sibling setter exists, but it does not explicitly state 'use this when you need to check your threshold' or mention when not to use it. No alternatives are named.

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