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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds the context 'specific curated collection' and 'vault creation', but does not disclose behaviors like pagination, return structure, or error conditions. It provides some added context but not rich behavioral detail.

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 a single, front-loaded sentence that immediately states the action and target. It avoids filler and repeats nothing from the schema or annotations, making it highly efficient.

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 simplicity (one parameter), strong schema coverage, and rich annotations, the description is fairly complete for its purpose. It explains what it does and why it would be used. The lack of an output schema means the description could have mentioned the return format, but the phrase 'Get all assets' adequately conveys the core result for this context.

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?

The input schema already provides a clear description of collectionName with examples and a hint to list collections first, so schema coverage is 100%. The description's reference to 'specific curated collection' reinforces the parameter's meaning but does not add substantial new information beyond the schema.

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 uses a specific verb 'Get' with a clear resource 'all assets within a specific curated collection' and adds context 'for vault creation'. It distinguishes itself from sibling tools like emblemListCollections (lists collections) and emblemResolveAsset (resolves individual assets) by focusing on retrieving all assets in a collection.

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 implies when to use the tool: during vault creation, and the schema parameter description explicitly advises 'use emblem list collections first', which provides actionable sequencing. However, it does not explicitly mention alternatives or when not to use this tool, so it stops short of full guidance.

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