add_to_collection

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

Without annotations, the description provides no behavioral details such as side effects, idempotency, or authorization needs. It does not disclose whether adding a design already in the collection has any effect, nor does it mention error conditions.

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 extremely concise at one sentence. However, it sacrifices necessary detail for brevity, making it borderline under-specified.

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 annotations and no output schema, the description is incomplete. It lacks information about return values, success/failure indicators, and potential errors, which are critical for a mutation tool.

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?

With 0% schema description coverage, the description adds minimal meaning. It implies 'design' and 'collection' but does not explain the parameters design_slug and collection_id beyond their names, leaving their formats and sources unclear.

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 a design) and target (to one of your collections). It effectively distinguishes from sibling tools like list_collections or upload_design, though it lacks nuance (e.g., whether it creates a new association or moves).

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 on when to use this tool versus alternatives, nor any conditions or prerequisites. The description does not indicate when not to use it or suggest other tools for related tasks.

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