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

The description mentions a cost of $0.005, which is a behavioral trait. However, without annotations, it fails to disclose other important traits such as whether it is a read-only operation, authentication requirements (api_key purpose is unclear), rate limits, or side effects. The cost disclosure is insufficient for full transparency.

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 very concise (two short sentences), which is efficient. However, it could include more useful information without becoming overly long, such as clarifying the api_key parameter. It earns a mid score for being compact but lacking necessary 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?

Given the lack of annotations, output schema, and parameter description, the tool is insufficiently documented. While the tool is simple, the description omits crucial context like the return format, balance meaning, and authentication steps, leaving the agent with significant 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?

The description adds no meaning to the single required parameter 'api_key' beyond the schema's type definition. With 0% schema description coverage, the agent has no explanation of what the key represents or how it should be obtained, making parameter interpretation impossible.

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 tool checks an agent's CryptoBoss API balance. It uses a specific verb and resource, making the purpose evident. However, it does not explicitly differentiate from sibling tools like 'check_usage' or 'check_approvals', but the balance focus is distinct.

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 provides no guidance on when to use this tool versus alternatives (e.g., 'pay_agent' to add funds or 'get_portfolio_value' for portfolio balances). There is no mention of prerequisites or context that would help an agent decide to invoke it.

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