createCollectionRequest

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

Annotations already indicate it's a write (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds one behavioral detail: if 'name' is omitted, it creates with a blank name. No other side effects, auth needs, or rate limits are mentioned.

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 short (two sentences plus a note) and starts with the core purpose. Every sentence adds value, though the note could be integrated into the main text. No fluff.

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?

With 15 parameters and no output schema, the description should mention what the tool returns (e.g., the created request object or ID) and any prerequisites (e.g., collection must exist). It does not. The complex input schema is not addressed beyond the schema itself.

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's note about 'name' is redundant with the schema's own description. No additional parameter semantics are provided beyond what the schema already includes.

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 the action ('creates a request in a collection') and distinguishes it from siblings like 'updateCollectionRequest' and 'createCollection'. It is specific about the resource and action, though it does not explicitly require an existing collection.

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 is provided on when to use this tool versus alternatives (e.g., updateCollectionRequest). The only note is about the 'name' property, which is more of a behavioral tip than usage direction.

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