Get cabinet

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered. The description adds workflow context (call before writes to verify currency and the write gate), but never explains what a gate state means or what happens if the gate is closed, so added value is modest.

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?

Two sentences with no waste: action first, then usage trigger and alternative, then returned fields. Nothing requires trimming.

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?

An output schema exists, so the trailing field list (owner_id, cabinet, currency, money, balance, write_gate) is partially redundant, and it is the only thing slightly bloating the description. For a zero-parameter read tool with full annotation coverage, the purpose and routing information are otherwise complete.

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, so the baseline is 4. The currency values mentioned (GRAM/EUR/XTR) describe returned data rather than inputs, and the agent has no parameter ambiguity to resolve.

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?

States a specific verb and resource ("Read the current cabinet card") and explicitly separates itself from the sibling that handles advertising data ("for the ad list use `get_ads`"). An agent can distinguish it from list_accounts/select_account without opening a schema.

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?

Gives an explicit when: "Use before any write to check currency and gate," and names the alternative for a closely related need ("use `get_ads`"). The trigger condition and the routing rule are both stated, not implied.

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