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

Annotations already declare readOnlyHint and destructiveHint=false, so the description's added value is the enforcement semantics: maxTradeUsd caps buys only, sells into USDC never count, cancelled buys release reservations, and paused blocks everything. It also discloses that data is resolved from the caller's API key with no way to query another wallet, and mentions platform rate limits. Minor gap: it doesn't say what a refusal/error response looks like, though that likely lives in the output schema.

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?

Front-loaded with the imperative and the READ-ONLY constraint, and the bulleted field breakdown is scannable. However, it is very long for a zero-argument getter, and much of the field-by-field explanation overlaps with the output schema that already exists — several clauses (e.g. the trailing restatement that this returns the current user's data) could be trimmed without losing meaning.

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 no-parameter, read-only tool with an output schema, the description covers everything an agent needs: what the fields mean operationally, how the daily volume math works, when trades get refused, and where the user must go to change limits. Nothing required for correct invocation 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?

Zero parameters, so the baseline is 4. The description spends its words on return-field semantics instead, which is a reasonable use of the space but is not parameter documentation.

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 the resource precisely — the trading limits the user set on the agent in the Moby app — and immediately marks it READ-ONLY. No sibling tool returns guardrails, and the description makes the scope unambiguous in the first clause.

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 tells the agent to read this before planning trades 'instead of discovering limits by refusal,' which is a concrete when-to-use trigger. It also explains that only the user can change the limits and that app_links.settings is where they do it, so the agent knows the correct escalation path rather than attempting a write.

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