save_to_inspiration

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

With no annotations, the description must disclose behavioral traits. It mentions 'bookmark' implying a write operation, but does not state side effects, restrictions (e.g., duplicate handling), or whether notes are saved. The return value is not mentioned.

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 sentence, front-loaded with the action. However, it is too brief and omits important details, making it incomplete rather than 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?

Despite having an output schema (as per context signals), the description lacks context on what the tool returns or any failure cases. For a simple tool with two parameters, more completeness is expected.

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 description coverage is 0%, yet the description adds no meaning for the parameters. 'post_id' and 'notes' are not explained beyond their names. The purpose of 'notes' and how 'post_id' relates to the feed are unclear.

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 action ('Bookmark'), the resource ('a post by id, from the current feed'), and the destination ('into saved inspiration'). It distinguishes the tool from related siblings like 'remove_from_inspiration' and 'list_inspiration'.

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 implies the post must be from the current feed, but does not explicitly state when to use this tool versus alternatives like 'add_artist' or 'reset_seen'. No 'when not to use' guidance is provided.

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