putCollection

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

Discloses that operation replaces contents, requires ID preservation to avoid recreation, and has 100MB size limit. No annotations to contradict; description carries burden well.

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 succinct sentences conveying essence upfront. Every word contributes: action, format, ID warning, size limit.

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?

Covers key behavioral aspects for a replacement operation with three parameters and no output schema. Sufficient for an agent to use correctly.

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 covers 100% of parameters with basic descriptions; adds value with ID warning and size constraint, enhancing understanding beyond schema fields.

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 'Replaces collection contents' with specific format and size constraint, distinguishing it from siblings like createCollection or getCollection.

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?

Provides important usage warning about ID values but does not explicitly state when to use vs. alternatives (e.g., putCollection vs. updateCollectionRequest). Implies usage context.

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