Favorite asset

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

Annotations already declare a destructive, non-idempotent, open-world mutation. The description adds a genuinely non-obvious behavior: unresolved references are materialized (saved as assets) before favorite state is applied. That is real value beyond the annotations, though it omits the confirm-gate requirement that the schema implies for this mutation.

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?

Two tight sentences with the core action front-loaded and the identifier guidance placed close behind. No filler, though the materialization clause is slightly compressed and could be clearer.

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?

For a 7-param mutation with a nested payload, mutually exclusive body inputs, and a confirm gate, the description is thin: it does not mention confirm, payload_file, idempotency, or how the body options interact. The rich schema compensates, keeping this adequate rather than deficient.

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 the schema already documents all 7 params including the nested payload and exclusivity rules. The description only restates the request_id/vector_id choice and adds no format, precedence, or exclusivity detail beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb+resource ('Favorite an asset') and clarifies the input shapes (request ID or vector ID). It implicitly separates itself from unfavorite_asset, but does not distinguish itself from sibling favorites like favorite_asset_collection or favorite_asset_character, which share nearly identical naming.

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?

It tells the agent which identifier to supply, which is practical input guidance, but gives no when-to-use framing, no exclusions, and no mention of the alternative favorite/unfavorite siblings. Usage is implied by the name rather than stated.

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