get_user_loan_details

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states 'Get on-chain details' implying read-only, but lacks specifics on return format, data freshness, or any side effects. Minimal value added.

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 extremely concise (7 words) but at the cost of omitting essential parameter context. It is not verbose, but the brevity hinders usability.

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 has one required parameter and no output schema, the description should at least clarify the parameter and the scope of 'details'. It fails to do so, leaving the agent with insufficient information to invoke the 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?

The sole parameter 'hub_id' is a number with no description. Schema description coverage is 0%, and the description adds no explanation of what hub_id represents (e.g., loan identifier, user ID). The agent cannot infer how to populate it correctly.

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 'Get on-chain details for a specific loan' clearly states the verb (get) and resource (loan details). It is direct and unambiguous, though it does not differentiate from similar loan-related tools like 'get_loan_events' or 'get_vault_loan'.

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?

No guidance is provided on when to use this tool versus the many sibling loan tools (e.g., 'get_loans', 'get_loan_events', 'get_vault_loan'). The description gives no context about prerequisites or scenarios.

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