Cite a web page

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

Annotations show readOnlyHint=false and openWorldHint=true; the description adds valuable context by explaining deduplication behavior and that quotes/notes attach to existing sources. It doesn't discuss error modes or auth requirements, but the dedup behavior is a key non-obvious trait.

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?

Three sentences, front-loaded with the core action and followed by the deduplication rule and the value proposition. No waste; every sentence carries distinct information.

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 no output schema, the description covers the key behavioral outcomes (dedup, note/quote attachment). It doesn't describe what the saved source object looks like or any rate limits, but for a 5-param tool with full schema coverage, it is largely complete.

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%, so the baseline is 3. The description adds meaning by explaining that quote/note are added to the existing source if the URL is already saved, and that the URL itself is deduplicated – semantics not evident from the schema alone.

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?

States a specific verb and resource: fetch a URL, extract bibliographic metadata, and save it as a source. Distinct from siblings like add_source and add_quote by naming the exact capture behavior.

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?

Provides clear context: 'the fastest way to capture a citation while browsing.' Explains the deduplication behavior, which frames when to use it versus add_source. However, it doesn't explicitly name add_source as the alternative or state when not to use it.

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