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

Annotations declare destructiveHint=true, so the safety flag is covered structurally, but the description adds no behavioral detail about which operations are irreversible, that buy consumes resources (expect_price_crumbs), or that idempotency_key guards replays. For a 12-parameter mutation tool the description leaves the risk profile almost entirely undisclosed.

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, purpose front-loaded, no padding. However it is telegraphic fragments rather than clear prose, and the semicolon-packed action list is hard to parse – brevity here shades into under-specification.

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?

With 12 parameters, no required fields, no output schema, and only a single destructive annotation, the description should carry most of the explanatory load. It instead provides roughly two lines and omits return shape, cost mechanics, and parameter meaning, leaving the tool largely opaque.

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 8% – only limit is annotated – and the description compensates only by paraphrasing the enum values as prose ('buy or split a plot; store or withdraw goods'). It never explains idempotency_key, expect_price_crumbs, resource, quantity, org, district, deed_id, all, or offset, so the vast majority of parameters carry no meaning anywhere.

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 categories it exposes (balance, deeds, capacity, goods) and enumerates the action modes (plots, buy, split, store, withdraw), so an agent can tell this is a land/goods management tool. It is terse and fragmentary, and it never explains what a 'holding' conceptually is, but the verb+resource pairing is present.

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?

It implies which action string to pass for each intent but gives no when-to-use context and never differentiates this tool from siblings like act, move, or reclaim. No prerequisites, costs, or exclusions are stated, leaving the agent to infer everything about routing.

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