Get Loan Summary

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

No annotations are provided, so the description carries the burden. It describes the return content (applicant details, amounts, status, etc.) but does not explicitly state whether the operation is read-only, requires special permissions, or has side effects. The behavior is implicitly a read operation, but the description lacks explicit disclosure.

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?

The description is a single well-structured sentence that states the purpose, resource, and key fields upfront. No extraneous words or fluff.

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?

Given the tool's simplicity (one required parameter, no output schema) and no annotations, the description provides sufficient context for an agent to understand its purpose and return content. However, the lack of an output schema and no detail on pagination or error handling leaves minor gaps.

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 one parameter (referenceNumber) described with an example. The tool description reiterates that the tool works by reference number, adding no new semantics beyond the schema. 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?

The description clearly states the verb 'retrieve', the resource 'full summary of a single loan application', the identifier 'reference number', and lists included fields like applicant details, amounts, status, eligibility, and assigned officer. This distinguishes it from siblings like GetLoanStatus (status only) and SearchLoansByPhone (search).

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 usage when a single loan summary is needed via reference number. However, it does not explicitly state when to avoid this tool or mention alternatives among the many sibling tools, such as GetLoanStatus for a lighter query. No exclusions or context cues are provided.

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