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

With no annotations, the description carries the full burden and does well: it discloses price ($10 USDC), chain/wallet, latency (<500ms), 60fps, joint hierarchy, and offers an alternate x402 payment route. It omits failure modes (what happens on invalid tx hash, whether payment is verified before or after data fetch), which keeps it short of a 5.

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?

Three dense sentences, front-loaded with what the asset is and its specs, then payment mechanics, then the cheap alternative. No filler despite carrying a lot of information.

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 5-param paid tool with no output schema and no annotations, the description covers cost, delivery protocol, and quality specs well. It does not describe what is actually returned (file/inline data, manifest, lesson scoping), which an agent needs when there is no output schema.

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 100%, so the schema already documents all five parameters. The description restates that the tx hash goes in payment_tx but adds no format or validation detail beyond the schema, so the baseline 3 applies.

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 concretely ('BVH skeletal animation') and names its target use cases (robotic_grappling_training, imitation_learning). It also implicitly distinguishes itself from get_trial_bvh as the paid full version. Lacks an explicit verb like 'retrieve', but the resource+format is unambiguous.

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 routes budget-conscious callers to get_trial_bvh as a cheaper alternative, and explains the payment paths. However, it gives no guidance on when to prefer get_bvh over other content siblings like get_mocap_sample or get_robotarget, or how lesson_path selection should be driven.

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