cowpin_get_balance

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It states the action ('check') which implies a read-only operation, but it does not explicitly confirm that it has no side effects, nor does it mention any authentication, rate limits, or network dependencies. For a balance query, the omission of explicit read-only confirmation is a minor gap.

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 front-loads the action and lists the three key pieces of information returned. Every word contributes meaning, with no fluff or repetition. It is optimally concise for an agent to parse quickly.

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 (no parameters, no output schema, no nested objects), the description fully covers what an agent needs to know: what it does and what it returns. The siblings are unrelated, so there is no missing context about alternative choices. The description is complete for its purpose.

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 tool has zero parameters, and the input schema is empty, so there is nothing for the description to elaborate on. The baseline for 0 parameters is 4, and the description correctly stays silent on parameters since none exist. No additional value is needed.

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 uses a specific verb ('Check') and names the exact resource (agent wallet) and the data it returns (micro-credit balance, available queries, on-chain USDC deposit address). This clearly distinguishes it from the sibling memory tools, which focus on saving and retrieving memories, so an agent can easily tell this is the balance tool.

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 clearly indicates this tool is for checking account-related information, and the sibling tools are all memory operations, making the appropriate context obvious. However, it does not explicitly state when to use this tool versus alternatives or mention any exclusions, so it lacks explicit usage guidance.

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