List, Diff, or Restore Manifest History

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

Annotations are all false, so description should disclose behavioral traits. It mentions 'verified immutable' but doesn't clarify whether restore is destructive or what side effects occur. 'Monotonically restore' is unexplained. No contradiction with annotations.

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?

Single sentence, no waste. Could be restructured for clarity (e.g., bullet list of actions) but remains concise.

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?

Tool supports three different actions but provides no way to specify which action to perform (no parameters). Output schema exists but description doesn't mention how actions are selected or what output to expect for each. Incomplete for a multi-action tool.

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?

Input schema has 0 parameters and schema coverage is 100%, so baseline is 4. No parameters to document; description doesn't need to add parameter information.

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 lists three actions (list, music-diff, restore) on manifest history, but uses jargon like 'music-diff' and 'monotonically restore' which lack clarity. It distinguishes from siblings as the only history tool but the exact purpose is vague.

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 context about prerequisites or typical use cases. The agent receives no help selecting this tool from the 20+ siblings.

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