bookmarks_add

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

No annotations exist, so the description must cover behavioral traits. It only states the basic action without disclosing auth needs, side effects (e.g., duplicate handling), rate limits, or any constraints. The presence of an output schema helps but is not leveraged in the description.

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, earning its place. However, it is overly terse and sacrifices necessary detail for brevity. It could be expanded to include parameter guidance without becoming verbose.

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 the tool's complexity (7 parameters, no annotations), the description is insufficient. It does not explain what a bookmark is, how type affects behavior, or the response format. The output schema exists but is not referenced, leaving the agent underinformed.

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?

With 0% schema description coverage, the description wholly fails to add meaning to the 7 parameters. It does not explain required fields like channel_id, title, type, or optional fields like emoji, entity_id, link, parent_id. The agent gains no semantic insight beyond the schema's property names.

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 'Add a bookmark to a channel,' specifying the verb (add), resource (bookmark), and location (channel). It distinguishes from sibling tools bookmarks_edit, bookmarks_list, and bookmarks_remove, which serve different purposes.

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 is provided on when to use this tool versus alternatives like bookmarks_edit or bookmarks_remove. There is no mention of prerequisites, context, or any conditions that influence tool selection.

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