add_to_collection

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

No annotations provided, and description fails to disclose key behaviors: whether the operation is idempotent, what happens if object already in collection, required permissions, or side effects. The single sentence adds no behavioral context.

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?

Description is short but underspecified. While concise, it lacks necessary information to be useful. Every sentence should earn its place; here one sentence does not sufficiently describe the tool.

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?

Tool is simple with 2 params and no annotations, but the description is still incomplete. It does not mention return values (though output schema exists), preconditions, or any contextual details that an agent needs for correct invocation. Falls short for a tool among many sibling tools.

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?

Both parameters have no descriptions in schema (0% coverage). The description adds no meaning beyond the parameter names (collection_name, object_name). An AI agent gets no help understanding valid values or format. Baseline should compensate for low schema coverage, but fails entirely.

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?

Description states verb and resource ('Add an object to a collection') but is generic. Does not differentiate from many related sibling tools like 'create_collection' or 'manage_object_construction', leaving ambiguity when to use this over alternatives.

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 vs alternatives. No description of prerequisites (object must exist, collection must exist), no exclusions or when-not-to-use.

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