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

Description adds batch processing behavior (1-50 IDs), response shape { results, errors }, and lists return fields. Annotations already indicate read-only and idempotent, and description does not contradict them.

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?

Single sentence covers purpose, key fields, usage, parameter spec, and response shape. No wasted words; every sentence adds value.

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?

Lists many return fields and error shape, but lacks explicit mention of authentication prerequisites or that loan_ids come from list_loans. Still, overall very informative.

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 has no description for loan_ids. Description specifies array format and size limit (1-50), greatly enhancing meaning beyond bare 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 clearly states the tool returns full loan contract detail by ID, naming the resource and method. It distinguishes itself from sibling openfinance_list_loans by specifying it is for deep-diving into a specific contract.

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?

Explicitly instructs to use after openfinance_list_loans for a specific contract, providing clear context. Could mention when not to use, but the guidance is sufficient.

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