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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds valuable behavioral context: it clarifies that wallet funds do not increase a Task's ceiling and that the tool cannot mint funds or spend another account's balance, which are important boundaries not captured by annotations.

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 three tightly scoped sentences with no filler. It front-loads the primary view option and moves through constraints and the alternative view efficiently, making it easy to parse.

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 simple read-only wallet tool with one enum parameter and an output schema, the description covers both views, the default, key limitations, and what information each view returns. The output schema handles return value documentation, so nothing critical is missing.

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 description coverage is 0%, so the description must carry the burden for the single view parameter. It does this well by explaining the meaning of both enum values (summary and activity) and identifying activity as the default, adding meaning beyond the bare schema.

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 states a specific resource (Hive Bucks wallet) and distinguishes two views: summary for balances and activity for transactions. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tools such as private_agent_budget or account_usage.

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 explains when to use view=summary versus view=activity, which is useful internal guidance. However, it does not state when to choose this tool over sibling tools or any prerequisites for calling it.

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