item_set_fade

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

The description discloses the special value -1 for unchanged and maximum 60s limit, but does not mention reversibility, side effects, or permissions. With no annotations, more disclosure would be beneficial.

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 extremely concise with a one-line purpose and structured argument list. Every sentence provides essential information without redundancy.

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 simple setter tool with 3 parameters and no output schema, the description covers all relevant details about arguments and constraints. It is complete enough for correct invocation, though it could mention if any return value or confirmation is provided.

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 description adds full meaning to all three parameters, including units (seconds), constraints (0 or more, max 60s), and special values (-1 for keep). Schema has no descriptions, so the description carries the entire burden effectively.

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 sets fade in/out for an item, with specific parameter details. It distinguishes itself from other item manipulation tools in the sibling list.

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 on when to use this tool versus alternatives. No exclusions or context provided beyond the basic function.

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