add_bookmark

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

Discloses beyond annotations: bookmarks are private, server-side, no public record, keyed by post URI, rate limiting. Annotation hints (idempotentHint, destructiveHint, openWorldHint) are fully explained 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?

Concise, front-loaded sentence, efficiently packs all key details (privacy, no-op, alternatives, auth, rate limit) without redundancy.

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?

Coverage of purpose, parameters, behavior, alternatives, constraints, authentication, and rate limiting is comprehensive for a simple bookmarking tool, especially with output schema present.

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 coverage is 100%, but description adds meaningful context: specifies URI format 'at://did/app.bsky.feed.post/rkey' and explains CID is optional and auto-resolved. Adds value beyond schema.

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 the specific action: 'Privately bookmark a post'. Distinguishes from siblings (remove_bookmark, get_bookmarks) and specifies scope ('Only posts can be bookmarked').

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?

Explicitly states when to use: to bookmark a post. Provides alternatives: 'Use remove_bookmark to remove and get_bookmarks to list.' Mentions no-op for already-bookmarked posts and authentication requirement.

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