edit_collection

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

No annotations are provided, so the description must fully disclose behavioral traits. It only explains parameter semantics but fails to mention mutation behavior, permission requirements, reversibility, error handling (e.g., invalid rating_key), or whether the tool returns any confirmation. This is a significant gap for a mutation tool.

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 front-loaded with the purpose. Parameter explanations are inline and avoid redundancy. Every sentence serves a purpose, with no wasted 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?

The description covers all five parameters adequately but omits information about the output or return value, error conditions, and how this tool fits into the broader collection workflow. Given no output schema, the description should at least hint at the result (e.g., confirms success). This limits completeness.

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?

The description adds substantial meaning beyond the input schema, which has 0% coverage. It clarifies default behaviors (e.g., empty string means no change for title, while None vs empty string for summary have different effects) and enumerates valid values for sort_order and mode. This directly compensates for the schema's lack of descriptions.

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 'Edit a collection's metadata' clearly identifies the verb (edit) and resource (collection). The subsequent parameter list clarifies which metadata fields are editable. However, it does not explicitly distinguish from sibling tools like create_collection or delete_collection, though the verb alone implies modification.

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?

There is no guidance on when to use this tool versus alternatives (e.g., add_to_collection for adding items, delete_collection for removal). No preconditions or context are provided, leaving the agent to infer usage from the parameter list alone.

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