add_to_collection

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the core action but does not disclose side effects, duplicate handling, error behavior (e.g., missing collection or photo), or whether the operation is reversible.

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 filler words. It is efficient, though it errs on the side of being slightly too terse given the absence of annotations and parameter documentation.

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 mutation tool with no annotations and 0% schema coverage, the description is too thin. An agent still lacks information about required preconditions, expected return behavior, and how to correctly format the photo IDs, even though an output schema exists.

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 0%, so the description must compensate for the two parameters. It clarifies that photo_ids identifies photos and collection_id identifies an existing collection, but it does not explain ID formats, the mixed string/integer type for photo_ids, or any constraints beyond 'existing'.

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 verb ('Add'), a resource ('photos'), and a target ('an existing collection'). It clearly differentiates from siblings like create_collection by emphasizing 'existing', so an agent can tell what this tool is for.

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 word 'existing' implicitly signals that this tool is not for creating a new collection, which points toward the sibling create_collection. However, there is no explicit when-to-use guidance, no mention of prerequisites (e.g., collection must exist), and no alternative routing.

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