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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful content scope (DOGE balance, house credit, entries, deposits) but discloses no further behavioral traits such as freshness, authentication requirements, or that this is strictly a no-side-effect lookup.

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 front-loaded sentence with no filler. Each phrase names a distinct piece of information an agent can expect from the tool.

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 zero-parameter, read-only tool with no output schema, the description conveys the expected return contents well: balance, credit breakdown, entries, and deposits. It leaves terms like 'house credit' and 'deposits' slightly open-ended, but the overall behavior is understandable without further detail.

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 takes zero parameters and the schema is an empty object, so parameter documentation is not needed. Baseline for zero parameters is 4, and the description appropriately focuses on what the tool reports rather than inputs.

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 names the resource ('your tab') and enumerates the data shown: DOGE balance, house credit vs deposited, recent entries, and deposits. It is clear this is a read-only view tool, though it lacks an explicit verb like 'view' or 'show'. It does not distinguish itself from similar state tools like pocket, inventory, or bonds.

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 such as deposit, pocket, or inventory. An agent must infer from the name and the mention of DOGE that this is the right tool. No exclusions or alternative routing are given.

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