get_loans

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

With no annotations provided, the description carries the burden and does disclose a key behavioral trait: it returns only active (not yet returned) loans, not the full loan history. It does not mention edge cases like missing member IDs, pagination, or ordering, but as a read-only listing tool these are less critical.

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 well-structured sentence front-loads the core purpose ('Lists all active loans') and immediately adds the filtering criterion and parameter scope. Every word is necessary, with no fluff or repetition.

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 simple read-only list operation with one required parameter and an existing output schema, the description covers the essential invocation context: what is returned, the filter, and how to scope it. No additional information is needed to call this tool 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 description coverage is 0%, but the description compensates by explaining that member_id is used to scope the result set to one member's loans. While it doesn't add format details, clarifying the role of the sole required parameter provides sufficient meaning beyond the raw schema.

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 uses a specific verb and resource ('Lists ... loans') and includes critical scoping ('active (not yet returned)', 'by member ID'). This clearly distinguishes it from sibling tools like get_book or return_book, which target different resources or actions.

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 implies when to use the tool: when you need a member's currently active loans and already have a member ID. However, it does not explicitly state exclusions or point to any alternative, leaving selection guidance mostly implicit.

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