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

The description strongly reinforces the read-only hint by explicitly stating 'Nothing is borrowed by this tool: no key, no transaction.' It also discloses the two confirmation modes (Go mode vs Builder mode) with their respective URLs, which adds valuable behavioral context beyond the annotations.

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 front-loaded with the core action, followed by the key non-destructive clarification, and ends with a concise usage guideline. Every sentence earns its place with no redundancy.

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 read-only operation with full schema coverage and no output schema, the description provides all needed context: what it does, what it returns (two links), safety guarantees, and when to use it. Nothing an agent needs to call it correctly is missing.

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 coverage is 100%, so the schema already documents all parameters including constraints and examples. The description adds the context that the tool checks whether the agent can borrow the specified amount for the specified days, but does not add parameter syntax beyond what the schema 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?

The description states a specific verb (prepare/check) and resource (a borrow on a Priors agent's credit line), and clearly distinguishes itself from any true mutation by emphasizing it returns confirmation links rather than executing a borrow. It's easy to distinguish from request_repay and other siblings.

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 clear usage condition: 'Use it when the user wants to borrow USDG for an agent they own.' However, it doesn't explicitly mention alternatives or when not to use it relative to siblings like request_repay.

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