update_collection_item

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

No annotations provided. Description only says 'Update an item' and defines fields_json. Fails to disclose permissions, required fields beyond schema, error handling, or side effects. For an update tool, this is a significant gap.

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?

Two sentences, front-loaded with action. Efficient but could add more value without becoming verbose. 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?

4 required parameters, no annotations, output schema exists but description doesn't mention return values. Incomplete for an update operation. Should explain how selector/unique_id identify the item and what the response contains.

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 has 4 required parameters with 0% description coverage. Description only explains fields_json as 'JSON object'. No explanation of project_id, selector, unique_id, or their roles. Schema lacks descriptions, so the description fails to compensate.

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?

Clearly states it updates an item in a custom collection section. The verb 'update' and resource 'item in custom collection section' are specific. It distinguishes from create/delete siblings by naming the action. However, 'custom collection section' could be clarified.

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 update vs create or delete. Siblings like create_collection_item and delete_collection_item exist but no comparative hints. Agent must infer usage from name alone.

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