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

With no annotations, the description carries the full burden, and it does disclose the most important trait: $0.10 USDC via x402, charged only on success, which tells the agent payment/auth is required and failures are free. However, it says nothing about input validation, processing time, or how results are returned (base64 vs URLs), so significant behavioral gaps remain.

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 sentences, outputs stated first, price second, family context third — reasonably front-loaded with little waste. The family sentence is a touch long but earns its place by explaining the suite's purpose.

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 6-parameter rendering tool with no annotations, no output schema, and low schema coverage, the description omits how inputs are supplied (glb vs glbUrl), what the response shape looks like, and any constraints. Pricing is covered, but an agent still lacks what it needs to call this correctly.

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 only 33% (6 params, only 'glb' and 'lighting' documented). The description adds no meaning for size, upAxis, background, or the critical glb-vs-glbUrl choice (mutually exclusive? size limits?), so it fails to compensate for the schema gap.

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 the verb (render), the resource (GLB model), and the exact outputs (four PNG views at fixed angles, mesh stats and size). The family sentence ('turntable GIF, and isometric sprite sheets') implicitly distinguishes it from asset_render_sprites and asset_render_turntable, though it never names those siblings directly.

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?

States the intended use case ('thumbnails and previews') and that this is the catalog-views member of the render family, which implies when to pick it over turntable/sprite siblings. There is no explicit 'use this instead of X when Y' routing, so the agent must infer the choice.

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