Auto-detect band names for an asset from its reflectance statistics.

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

The description does not disclose whether the tool is read-only or modifies the asset state. Annotations show readOnlyHint=false but the description does not clarify the behavior (e.g., does it auto-update the asset or just return suggestions?). The lack of explicit mutation status or side effects reduces transparency.

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 sentence that repeats the title. It is short but not excessively verbose. However, it could be more informative without sacrificing conciseness. Adequate structure for a one-sentence description.

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 has three parameters (two required) and no parameter descriptions, the description should provide context on required data (e.g., asset must have reflectance statistics). The existence of an output schema is noted, but the description fails to mention input prerequisites or output expectations. Incomplete for a tool with moderate complexity.

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 0% and the tool description adds no meaning to the three parameters ('x-api-key', 'asset_id', 'item_id'). The unusual parameter 'x-api-key' is not explained (likely an auth field that is typically a header). No parameter formats, constraints, or roles are clarified.

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?

Tautological: description restates name/title.

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?

No guidance is provided on when to use this tool versus alternatives like 'items.set_asset_band_names'. The description does not mention prerequisites (e.g., asset must exist with reflectance statistics) or scenarios where detection is appropriate. This leaves the agent without context for selection.

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