asset_store

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

The description discloses that most actions are mutating (readOnlyHint=false) and mentions requirements and constraints. It aligns with annotations (readOnlyHint=false, openWorldHint=true) and adds context about caching and server interactions, though specific side effects per action are not detailed.

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 front-loaded with a clear summary, but the full list of all 12 actions repeats information from the schema enum. This makes it longer than necessary while still being organized. A more concise listing or referencing the schema would improve structure.

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 the tool's complexity (10 parameters, multiple sub-actions, no output schema), the description covers overall purpose, prerequisite conditions, and which actions work without authentication. It lacks details on return values per action but provides sufficient context for an AI agent to understand the tool's capabilities.

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%, so baseline is 3. The description adds minimal insight beyond parameter names; the note about Unity version and authentication is valuable but not linked directly to parameters. The nested importOptions object is only briefly described.

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 clearly states the tool manages Unity Asset Store assets and Package Manager integration, with a specific verb and resource. It distinguishes from siblings like 'manage_asset' by focusing on the Asset Store, and the listed actions reinforce the scope.

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 explicit prerequisites (Unity 2020.1+, logged into Hub/Editor) and notes which actions need authentication and that assets must be purchased before downloading. It doesn't explicitly mention when not to use or alternatives, but the guidance is clear and helpful.

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