updateCollectionRequest

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

Annotations already indicate destructiveHint=false and idempotentHint=true. The description adds valuable context: it acts like a PATCH (only updates passed values) and does not support folder changes. No contradiction with annotations.

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 but includes a link and three bullet points. The first sentence states the purpose, and the notes are relevant. Could be slightly tighter but well structured.

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 the complexity (15 parameters, no output schema), the description covers the core behavior and key limitations. However, it lacks details on success/failure responses, error conditions, or which fields are required beyond the schema. Adequate but not comprehensive.

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 coverage is 100%, so all 15 parameters have descriptions. The description adds nothing beyond the schema for individual parameters, only a link to external docs. Baseline of 3 is appropriate.

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 'Updates a request in a collection' with a specific verb and resource. It distinguishes from sibling tools like createCollectionRequest (create) and putCollection (full collection update) by noting its PATCH-like behavior and limitations such as no folder change.

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?

The description provides explicit usage notes: you must use a collection ID (not a collection), it does not support changing the folder, and it acts like a PATCH method. It does not explicitly compare to alternatives but implies its use for partial updates.

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