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

Annotations cover the safety profile (non-read-only, idempotent, non-destructive, closed-world), and the description adds context beyond them: the operation is free, ids must originate from this user's searches/lookups/saved creators, results surface on the Kolect website with CSV export, and quotes are recorded as 'my quote' visible only to the user.

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?

Front-loaded with the core action, then progressively adds prerequisites, downstream effects, and the quotes nuance — no sentence is filler. It is somewhat dense in a single block, which costs it the top score.

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?

With no output schema, the description compensates by describing where saved creators go and how they are used (website, CSV export, my-quote visibility). For a 4-parameter write tool this is nearly complete; only the return payload shape is left unstated.

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 75%, and the description still adds meaning: collection accepts a name or id and creates it when new; quotes record the rate the user actually got and are shown only to this user; search_id ties ids to their originating search. Only amount/currency/note remain purely schema-documented.

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+resource ('Save creators to the user's Kolect favorites') plus the optional collection scope, and implicitly distinguishes itself from list_saved_creators and lookup_creators by naming what it does rather than reads. An agent can identify the write path without opening the schema.

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?

Gives a concrete precondition: creator ids must come from this user's searches (with search_id), lookups, or saved creators — a real when-to-use rule. It does not explicitly name sibling alternatives (e.g., when to prefer lookup_creators first), so it falls short of a full routing rule.

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