Add Collection to Favorites

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

Annotations (readOnlyHint=false, idempotentHint=false) already signal a mutating, non-idepotent operation, but the description adds no behavioral context beyond that. It does not disclose whether re-adding an already-favored collection fails or silently succeeds, what happens if the collection does not exist, or whether the favorite is per-user. No contradiction with annotations, but no added value either.

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, front-loaded sentence with no wasted words. It borders on redundancy with the tool name and title, but it remains an efficient and complete sentence rather than a tatuological stub.

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?

For a tool with one fully documented parameter and no output schema, all required calling informtion is present: what the tool does and what to pass. However, it omits useful context such as the existance of the inverse sibling for removal, repeat-call behavior, and user scopcing of favorites, which would help an agent use it correctly.

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 100%, so collId is already documented as 'Collection ID' in the schema. The description merely echoes 'collection' without adding extra meaning or constraints beyond what the schema provides, matching the baseline for fully documented parameters.

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 states a specific action ('Add') and a clear resource ('collection' to 'user favorites'), making the core operation unambiguous. However, it does not explicitly distinguish itself from siblings, particularly the inverse transkribus_coll_remove_favorte, leaving the differentiation to the tool name and title.

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 offers no guidance on when to use this tool versus its alternatives. It does not mention the inverse operation transkribus_coll_remove_favorte, nor any conditions or prerequisites (e.g., ownership, authentication, or whether favorites are user-scoped).

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