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

With no annotations, the description carries full burden and does disclose the key traits: API Key required (auth), read-only nature, that each component returns raw JSON, and that writes live elsewhere. It omits pagination, rate limits, or freshness semantics, but covers the essentials for a no-argument snapshot.

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 tight lines: the first front-loads what is returned and the auth requirement, the second handles scope boundary (read-only vs writes). Every clause carries information; no filler.

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 parameterless, read-only snapshot with no output schema, the description is complete: it names the returned datasets, notes they are raw JSON, states the auth requirement, and clarifies the read/write boundary. Nothing an agent needs to invoke it correctly 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?

The tool takes zero parameters and the schema is empty, so there is nothing for the description to disambiguate. Baseline 4 applies since no parameter meaning is required.

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 resource (the owner's market data) and enumerates exactly the four sub-resources it snapshots (deals/mine, deeds/mine, intents/mine, intents/received) with parenthetical glosses. An agent can immediately tell this is a read-only aggregate view, distinct from write-oriented siblings.

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?

Explicitly frames the tool as a read-only snapshot and routes write operations (withdrawing intents, declaring deals) to REST endpoints, naming the concrete routes. This gives clear when-not guidance for mutations, though it offers no differentiation against read-oriented siblings like zengzhi_account_overview.

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