get_user_loan_count

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

No annotations exist, so the description must fully disclose behavior. It does not specify what 'wallet' means (user's own or arbitrary), whether it counts active/overdue/all loans, or the return type. Lacks essential behavioral context.

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?

A single, unambiguous sentence. Extremely concise and front-loaded with no wasted words.

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?

Despite no parameters, the description does not explain the return value format, edge cases (e.g., no loans), or which wallet is referenced. Given the complexity of the tool's context (multiple loan-related siblings), this is insufficient for reliable agent selection.

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?

Input schema has 0 parameters, so the description does not need to add parametric detail. According to rules, baseline is 4. No additional semantics required.

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?

Description states 'Count of loans for the wallet', which indicates the tool returns a numerical count. The verb 'get' in the name and resource 'loan count' make the purpose reasonably clear, but the phrase is a noun phrase rather than an imperative, which slightly reduces clarity.

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 on when to use this tool versus siblings like 'get_loans' or 'get_user_loan_details'. No context about prerequisites, applicable wallets, or alternative tools is provided.

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