manage_asset_library

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

With no annotations, the description discloses key behaviors: use of a fleet subprocess Blender, environment variable dependencies, that HDRIs set world environment, and that Sketchfab imports require downloadable models. Missing details on error handling or rate limits, but still above average.

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?

The description is extremely concise, using a portmanteau label and a bulleted list of operations. Every sentence conveys necessary information without redundancy.

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?

Given 13 parameters and 6 operations, the description covers each operation's purpose, prerequisites, and parameter hints. The existence of an output schema reduces the need for return value explanation. Minor gaps exist (e.g., pagination details for Poly Haven search), but overall it's comprehensive.

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 coverage is 100%, but the description adds context by grouping parameters under operations (e.g., 'polyhaven_import: Download + import...'). This clarifies how parameters interact beyond the schema's basic descriptions.

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?

The description explicitly states the tool covers 'Poly Haven + Sketchfab asset discovery and import' and lists six operations with clear verbs. It distinguishes from sibling tools (e.g., blender_import, list_local_models) by focusing on external asset libraries.

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?

The description provides operational details and prerequisites (e.g., env vars for Sketchfab, token requirements for imports). It implicitly guides when to use each operation, but lacks explicit comparisons to siblings or 'when not to use' conditions.

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