add_to_collection

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the mutation is expected. The description adds the return format (success/message/data) but does not disclose side effects, failure modes, or whether the collection is created if missing. This is adequate given the simple operation, but not rich.

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 and well-structured, with a one-line summary, a return format section, and a code example. No redundant text; every element serves a purpose.

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?

The tool is simple (2 string params, no nested objects) and has an output schema, so little beyond the basics is needed. However, the description could be more complete by clarifying the relationship to existing collections/objects and any error behavior, especially given the large set of sibling tools in the Blender domain.

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%, and the description does not explain the parameters beyond their names. 'collection_name' and 'object_name' are self-explanatory at a high level, but no details are given about what constitutes a valid name, whether the object must already exist, or how collections are referenced. The example shows sample values but adds no semantic depth.

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 clearly states 'Add an object to a collection' with a specific verb and resource. It distinguishes from sibling 'create_collection' (which creates collections) and 'construct_object' (which creates objects), though it does not explicitly mention the relationship to existing objects/collections.

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. It does not mention prerequisites (e.g., collection must exist), nor does it contrast with related tools like 'create_collection' or 'manage_object_repo'. The example provides usage context but not decision criteria.

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