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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered by structured data. The description adds useful domain semantics (pool-based lending, and that loan records include retired peer-to-peer loans), but says nothing about pagination, filter interaction, or result shape.

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?

Three sentences, front-loaded with the core action and its returned fields. The trailing sentences provide interpretation context for loan provenance rather than padding, though the historical P2P aside is tangential to invocation.

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 tool with no output schema, the description usefully enumerates what the response contains (counts, loans, liquidity, utilization, APR, events). Combined with annotations covering safety and a fully documented schema, an agent has what it needs to call it correctly.

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% with all five parameters, including the status enum and limit bounds, fully documented in the schema itself. The description adds no filter syntax or format detail beyond what the schema already provides, so baseline 3 is appropriate.

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 ('Get an overview of the Fabrica lending market') and enumerates the returned content (loan counts, loans, pool liquidity/utilization, APR, recent events), which clearly separates it from point-in-time siblings like get_borrow_quote. It stops short of explicitly naming which sibling to prefer, so it lands at clear-but-undifferentiated.

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 never says when to call this versus alternatives such as get_borrow_quote or get_protocol_stats, nor does it state prerequisites or when it is not appropriate. The only usage signal is the implicit 'you want market data' framing of the returned fields.

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