item_set_enabled

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

With no annotations provided, the description carries the full burden. It states the core effect (enable/disable) and adds the 'muted/unmuted' nuance, but it does not disclose side effects, required permissions, reversibility, or behavior when item_name is ambiguous. This is adequate for a simple setter but not rich in 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 concise sentence that directly states the function. It is front-loaded and contains no filler, earning every word.

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?

The tool has four parameters, with track_type and track_index optional. The description does not explain when these are needed to disambiguate items with the same name across tracks, which could lead to incorrect invocation. The presence of an output schema covers return values, so that aspect is complete, but the disambiguation guidance is missing.

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 schema descriptions cover 100% of the parameters, so the baseline is 3. The description adds no additional meaning beyond the schema; the 'muted/unmuted' hint is also present in the schema's 'enabled' parameter description. Thus, the description does not compensate further.

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 the tool's function: enabling/disabling a timeline item, with the parenthetical '(muted/unmuted)' providing useful semantic context. This distinguishes it from sibling tools like timeline_set_track_enabled, which operate at the track level.

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 gives no explicit guidance on when to use this tool versus alternatives, such as timeline_set_track_enabled or item_set_property. The implied usage from the name and description is clear enough for a simple setter, but there is no exclusionary or comparative guidance.

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