mosaic_watchlist_add_item

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

Description confirms idempotency, matching the idempotentHint annotation. No contradictions, but does not disclose additional behaviors like error handling or side effects beyond what annotations already indicate.

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 concise sentences with no wasted words. The first sentence states purpose, the second adds key behavioral detail.

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 annotations and presence of an output schema, the description is largely complete. It could mention that the watchlist must exist, but overall sufficient for use.

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 lists the allowed entity types (target, indication, etc.), adding meaning beyond the schema's property descriptions. The idempotency note is also helpful. Schema description coverage is 0%, but property descriptions exist, so description provides supplementary context.

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?

Clearly states it adds a watched entity to a watchlist, listing the specific entity types. Distinguishes from sibling tools like mosaic_watchlist_create (create list) and mosaic_watchlist_get (get 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?

Idempotency is mentioned, but no explicit 'when to use' or 'when not to use'. Context implies it's for adding items to existing watchlists, but no prerequisite (e.g., watchlist must exist) is stated.

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