createMock

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

With no annotations, the description carries full burden. It discloses the UID format and workspace requirement, but lacks details on permissions, side effects, success/failure outcomes, or whether the collection must exist. The nested object's internal structure is partially described but could be more explicit.

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 two sentences: the first states the primary action clearly, and the second provides key parameter guidance. No unnecessary words, fully front-loaded, and efficient for an AI agent.

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 tool creates a mock server with a nested object parameter and no output schema. The description covers the input format and workspace, but does not explain what happens after creation (e.g., return value, how to access the mock) or provide expected behavior. Adequate but incomplete for a creation tool.

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 description coverage is 100%, so the description adds only modest value by specifying the collection UID format (ownerId-collectionId). The workspace param description is essentially restated. Overall, it supplements rather than significantly extends the schema.

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 verb 'Creates' and the resource 'mock server for a collection', and distinguishes it from sibling tools like updateMock and publishMock by focusing on creation. It also specifies the unique identifier format (collection UID as ownerId-collectionId), adding precision.

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 implies usage by stating to use workspace param and collection UID, but does not explicitly contrast with alternatives like createCollection or updateMock. No when-to-use or when-not-to-use guidance is provided, leaving the agent to infer context.

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