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

Annotations indicate the tool is not read-only (readOnlyHint=false) and not destructive. The description adds context about costs, tiers, and optional features like Soul Whisper, implying metadata embedding. However, it does not explicitly state whether the tool modifies the asset in place or simply returns generated metadata, leaving room for confusion about side effects.

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 concise and well-structured, starting with the core function, then detailing tiers, and finally optional features. It uses a bullet-like format with parentheses for cost. One minor improvement would be to separate cost info from the description, but overall it is efficiently written.

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 absence of an output schema, the description should explain what the tool returns. It describes the generated metadata for each tier but does not specify the return format or whether it modifies the asset. This is a significant gap for a tool with 9 parameters and no output schema, making it only partially complete.

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%, with each parameter having a clear description. The tool description adds some high-level context about customization but does not significantly enhance understanding beyond what the schema already provides. The baseline score of 3 for high coverage 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?

The description clearly states it is an AI-powered artwork analysis tool with two distinct tiers, specifying the outputs for each. This differentiates it from sibling tools like infuse_metadata, which likely handle raw metadata injection rather than AI generation. The verb 'enrich' combined with the tier details leaves no ambiguity about the tool's purpose.

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 no guidance on when to use this tool versus alternatives such as infuse_metadata or other metadata tools. There is no mention of prerequisites, when not to use, or how to choose between this and similar tools. The focus is entirely on the tiers, not on usage context.

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