get_loan

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

No annotations are provided, so the description carries the burden. It discloses the authentication requirement (any Floe API key), which is a useful behavioral detail. However, it does not mention whether the operation is read-only, error conditions, or return format. For a simple getter, the auth disclosure is a positive but not exhaustive.

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 two sentences, front-loaded with the purpose, and includes the essential auth note. Every word earns its place; no unnecessary detail.

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 getter with no output schema or annotations, the description is largely complete: it explains what the tool does, the parameter, and a key requirement. It could potentially mention the shape of the returned details, but the name 'get_loan' and the word 'details' reasonably imply a full loan object. The description is adequate without being exhaustive.

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%, so the parameter is already documented as a numeric loan ID. The description reiterates this ('numeric ID') but adds no new semantic meaning 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 it retrieves details of a specific loan using its numeric ID. This distinguishes it from sibling tools like get_user_loans (which lists loans) and get_loan_health/get_loan_state (which focus on specific aspects). The verb 'Get' and resource 'loan' are explicit.

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 context: when you need a single loan's details by ID. It does not explicitly mention alternatives or exclusions (e.g., 'for listing use get_user_loans'), but the specificity of 'by its numeric ID' provides clear guidance for when this tool is appropriate.

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