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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the 'Read-only' sentence repeats structured data rather than adding to it. The description does not mention freshness, caching, or whether figures are real-time, but with annotations covering the safety profile the lower bar is met.

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?

A single front-loaded sentence with no filler; the long enumeration is justified because there is no output schema and each named figure is genuinely informative. It is slightly list-heavy but every item earns its place.

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, enumerating the returned fields (liquidity, principal out, total assets, reserve, fees, bad debt, agent count, loan counts, loan terms) is exactly the compensating detail an agent needs. Combined with annotations that cover the safety profile and a zero-parameter schema, the definition is close to complete; only freshness or units are left implicit.

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 takes zero parameters, so there is nothing to document and the baseline of 4 applies. The description correctly spends no words on inputs.

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 specific verb and resource ('Show the Priors credit pool's current figures') and enumerates exactly which figures are returned, so an agent knows precisely what this tool yields. It does not explicitly contrast itself with siblings such as recent_activity or agent_record, which is the only thing keeping it from a 5.

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 statement of when to call this versus alternatives, and no prerequisites or exclusions. The 'Read-only' note hints that it is safe to call freely, but the agent must infer that this is the tool for inspecting aggregate pool state rather than a specific agent's record.

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