Add entities to collection

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

No annotations are provided, so the description carries full burden. It only discloses that creatorUserId is required and can be set via env var. It does not mention side effects, reversibility, permissions needed, or behavior if the collection does not exist. As a mutation tool, this is insufficient transparency.

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 concise with two sentences: the first states the purpose and lists supported entity types, the second provides a crucial param hint. No unnecessary words.

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 3 parameters, low schema coverage, no annotations, and no output schema, the description is incomplete. It does not explain the required structure of the entities array, error conditions, or what happens if the collection is missing. An agent would need additional context to use this tool reliably.

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 low (33%). The description adds value for creatorUserId by explaining the env var fallback. However, for entities and collectionName, it adds no semantic detail beyond the schema. The nested structure of entities (entityId, entityLot, information) is not explained, and the requirement that entityId be an existing ID is absent. The description compensates partially but not fully.

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 the action: 'Add metadata, games, exercises, workouts, templates, or measurements to a Ryot collection.' This distinguishes it from siblings like adding to specific lists (watchlist, backlog) and from creating a new collection (ryot_create_collection). However, it could explicitly mention that it adds to an existing collection, which is implied but not stated.

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. For example, when should one use add_to_collection vs add_movie_to_watchlist or add_game_to_backlog? No exclusions or prerequisites are mentioned, leaving the agent to infer usage from context.

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