list_loans

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

No annotations are provided, so the description carries the full disclosure burden. It does useful work by stating the sort order and the default filter (active, i.e. not returned), but it says nothing about pagination, result limits, or whether historical/returned loans remain retrievable. An output schema exists, so not describing return fields is acceptable.

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 short sentences with zero filler, and the ordering constraint is stated up front before the filtering default. Every clause carries information the agent needs.

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 single-parameter read tool with an output schema, the description covers purpose, sort order, and default filtering, which is most of what an agent needs. The remaining gap is pagination/result-size behavior and the explicit relationship to sibling listing tools.

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%, so the description must define active_only itself, and it does: the default is 'only active (not returned)', which explains both the parameter's meaning and its default value. The negative case (what setting it to false yields) is only implied, keeping it short of a 5.

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 names a specific verb and resource ('List loans') and states the ordering ('newest last'), so an agent immediately knows this is the general loan-listing read. It does not explicitly distinguish itself from the sibling list_overdue, leaving the agent to infer that this returns all loans while that one returns a subset.

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?

It gives an implied usage rule by stating the default scope ('Default shows only active (not returned)'), which tells the agent what happens if no parameter is passed. However, it never says when to prefer this over list_overdue or the mutation siblings like renew_loan, and it gives no guidance on when to flip active_only to false.

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