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

Annotations already declare readOnly, idempotent, and open-world, so the safety profile is covered. The description adds real behavioral value by decomposing what "pending" includes across three operation types, which the annotations cannot convey. It stops short of describing pagination or result shape, but adds meaningful context beyond structured fields.

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-loads the core purpose then the enumeration, then usage triggers, then the parameter requirement. Slightly run-on but every clause (especially the three-category breakdown and the pre-action cue) earns its place.

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 read-only, single-parameter tool with no output schema, the description covers what is retrieved (three categories), when to call it, and the required input. Only minor gaps remain around result shape/pagination, which are less critical given annotations already establish the read-only nature.

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?

Single required parameter with 100% schema coverage, so the schema already documents the address format and example. The description only restates the requirement (truncated as "Requires an XRPL r... address"), adding no new format or constraint detail. Baseline 3 is appropriate.

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?

Names a specific verb (get) and resource (pending offers/domain operations) and enumerates the three distinct categories it covers: incoming offers, outgoing offers, and paid-but-not-minted orders. This lets an agent distinguish it from siblings like check_order_status or get_portfolio without opening the 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 concrete trigger phrasing ("do I have any pending transfers?", "what offers are waiting on me?") and a workflow cue (call before suggesting accept/cancel/continue-mint). It does not name the adjacent alternative check_order_status or state when not to use it, so it stops short of full routing guidance.

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